The setup

• An AI coding agent drove a dedicated Chrome profile for the company through the Chrome DevTools protocol. It reads the page's accessibility tree, then clicks and types by element id.
• The rules: free plans only; Google sign-in first, email and password otherwise; sign-in codes read from the company inbox; no reviews, no votes, no invented numbers.
• Every site got one row in a table: how we signed in, a status, and the one step left. Passwords went to a local file outside the repository, never into the table or the Git history.

1. A 200 that meant failure

G2's Add Product form takes a name, a domain, a description and a logo. The POST carried every field and came back with HTTP 200, and the page said "Something went wrong while saving your product". The status code looked healthy.

An automation that waits for a success phrase is easy to fool here. One of our waits matched G2's own "conditionally approved" boilerplate and looked like success, until a screenshot showed the error banner. Assert on something only a success can produce, such as a new URL or a record id, and look at the page when it matters.

We tried six times from a clean start with the same result. Only G2 can say why.

2. A field that was blank after the lookup

On the same form, the Vendor Name was empty after the domain lookup finished, although we had filled it. Typing it again with real keyboard events, after the lookup, kept it.

3. Controls that are not the input

• Styled radios. The radio's own element would not take a click. Its label did.
• A Vue multiselect on a project form (the tech-stack field). Focusing its hidden search input with a script, typing the value and pressing Enter selected it.
• File uploads. The browser tool only accepts files inside the project directory, so the screenshots were staged in a git-ignored folder first.

4. A .bd domain that a validator would not accept

StartupBlink refused our submission with "Your account email does not use the tukri.bd domain, so we cannot confirm you represent this company", although the account email is info@tukri.bd.

Our first guess was the Public Suffix List, the list that tools use to decide where a registrable domain starts. Rather than assume, we checked the current list:

curl -s https://publicsuffix.org/list/public_suffix_list.dat | sed -n '/^\/\/ bd :/,/^$/p'

It names bd and a fixed set of second levels: ac.bd, ai.bd, co.bd, com.bd, edu.bd, gov.bd, id.bd, info.bd, it.bd, mil.bd, net.bd, org.bd, sch.bd and tv.bd. There is no wildcard, so tukri.bd is not a public suffix, and a validator using the current list would treat it as an ordinary registrable domain. The guess was wrong, at least for today's list.

We still do not know why StartupBlink rejected it. G2's save error is on the same domain, which may be a coincidence. We have left both for their support teams. If you have seen a .bd domain trip a validator, we would like to know what it was.

5. Where the agent stopped on purpose

• CAPTCHAs and bot walls. Nine sign-ups ended at an image puzzle, a "verify you are human" box, a bot-block page, or a sign-in that looped back to itself. We did not try to get around them.
• Personal declarations. Boxes such as "I am 16 or older" and "I declare that this information is truthful" were refused by the agent's permission system when ticked on a person's behalf, even after a blanket "do everything as me". The ticks that had been approved by name (Terms and Privacy for one site) went through. We think that is right: a statement made under a person's name is theirs to make.

6. The log is worth more than the clicks

"Submitted" is not "live", and "account made" is not "listed". Each row says what exists, what does not, and the one step left. That is how we know that 13 submissions are waiting in review queues, instead of claiming 13 listings.

It also made a mistake cheap to fix. Our first screenshots came from the repository and showed Bangla product names and the taka sign, which do not belong on English listing pages. Because every site had a row, we could find each place they had been uploaded and replace them with English-only images.

Tukri is at tukri.bd, with a free plan.

Disclosure: we are the Tukri team. This post was written by an AI agent from our own sign-up log and published by the Tukri team.

Here are two plain CSV templates you can open in Google Sheets or Excel today:

You can get both files from this public gist: https://gist.github.com/tarikmanoar/e932cb88f0bd95334b257175f51bc787

Both files are saved as UTF-8, so Bangla text survives. In Excel, open them with Data > From Text/CSV > File origin: 65001 (UTF-8) if the Bangla looks broken.

1. The dues ledger (baki-khata-ledger.csv)

One row per event: a credit sale or a payment, never both.

Let the sheet do the running balance

In Google Sheets, with the header in row 1 and the data from row 2, put this in G2 and fill it down. It totals that customer's credit minus their payments up to the current row:

=SUMIFS($E$2:E2,$B$2:B2,B2)-SUMIFS($F$2:F2,$B$2:B2,B2)

For everyone's total due on one line:

=SUM(E2:E)-SUM(F2:F)

For one customer's current due, with the name in J1:

=SUMIFS(E2:E,B2:B,J1)-SUMIFS(F2:F,B2:B,J1)

Habits that make a ledger work

1. Write the due down the moment you give it. A due added at night from memory is a due that's half-remembered.
2. One customer, one spelling. "Karim Mia" and "Karim bhai" become two people to a formula.
3. Always ask for a date. "Next week" becomes promised_date, and you sort by it every morning.
4. Record part payments. A customer who pays 500 taka of 910 should see 410 taka left, not "still owes".
5. Share the history, not only the total. A customer who sees the dated rows argues less than one who hears a number.

2. The product list (tukri-product-starter.csv)

These are the eleven columns of the Tukri product importer:

sku,name,name_bn,category,unit,barcode,cost_price,sale_price,stock_qty,low_stock_threshold,is_active

• Required: name, unit (Pieces or pcs), cost_price and sale_price.
• Money: taka with up to two decimals and no symbol, so 210.00, not a currency sign in front of it.
• is_active: exactly YES or NO.
• The unit must already exist in the shop; the importer never invents one.
• Leave unknown cells empty. Don't guess barcodes or stock.

The full column list covers variants (sizes and colours), batches and expiry dates, packs (a box of 12) and warranties. It's in the public guide, along with a ready-made file:

• Guide: https://tukri.bd/products/import-guide
• Full template: https://tukri.bd/products/import-template.csv

When a spreadsheet stops being enough

A sheet is a good start. It gets hard when:

• several people write in it at once;
• you want to text a customer their exact due from your phone;
• you need to bill at the counter while the internet is down.

That's the gap Tukri fills. It's a Bangla-first POS, stock and dues-book app for small shops in Bangladesh, and it runs in the phone's browser and works offline. Its Free plan includes the digital bakir khata.

• Digital dues book: https://tukri.bd/tali-khata
• How to track customer dues: https://tukri.bd/learn/track-customer-dues
• Plans and limits: https://tukri.bd/pricing

Disclosure: this article and the templates come from the Tukri team, the people who build Tukri. The templates are free to use, copy and change. No sign-up is needed for the CSV files.