The first version of any B2B platform has a login page. Then a dashboard. Then, if the product touches anyone outside the office, a long quiet argument about why nobody is using it.
AutoKon verifies construction progress with photo evidence and uses that evidence to gate contractor disbursements across thousands of housing units. The evidence has to come from the site, from people standing in the mud with a phone, often on a patchy connection, often not the same people from one week to the next.
I did not build them a portal. They submit over WhatsApp.
Count the real cost of an account
A portal looks free when you are the one building it. The cost lands somewhere else:
- Someone has to create an account for every field worker, and deactivate it when they rotate off.
- Someone has to train them, in person, on a screen they will use a handful of times.
- The app has to go on a phone that may already be near full.
- Each of those steps is a place where the evidence does not get submitted, which means a disbursement does not get processed, which means somebody’s payment is late.
None of that appears in a sprint estimate. It appears in adoption.
Meanwhile every one of those workers already had WhatsApp open, already knew how to send a photo, and had used it that morning. The interface was installed and understood. The only question was whether I was willing to meet it.
What the architecture actually looks like
Field submissions come in through a WhatsApp-first flow built on n8n and Botpress. The conversation collects what the record needs (which unit, which stage, the photo) and hands a structured submission to the platform. From there the evidence enters the vision pipeline, gets graded by the evaluation stage, and lands in a five-role approval workflow.
Approvers work through guided chat too. Someone with four items to approve does not open a dashboard, find the queue and filter it. The items come to them in order, photo attached, decision reduced to a reply.
The dashboards still exist: S-curve and earned-value views for the people who plan and audit. Planning and auditing happen at a desk with a large screen. Capturing evidence and approving it do not. Two audiences, two surfaces, and only one of them had to be built from scratch.
Conversational does not mean unstructured
The failure mode of chat interfaces is that they accept anything and produce garbage, and a financial verification pipeline cannot afford that.
So the flow is guided rather than open. It asks one thing at a time. It rejects a submission with no unit reference instead of guessing. It never takes a free-text status in place of a photo. What reaches the platform is as structured as anything a form would have produced. The structure just lives in the conversation design instead of in a set of input fields.
Choosing WhatsApp did not remove the work of designing a data-entry flow. It moved that work, and made it harder, because you cannot lean on the layout to explain the model.
The leverage
I built and ran AutoKon’s platform solo, which made the channel decision unusually clear: every surface I built was a surface I would maintain, support and onboard people onto, by myself, indefinitely.
Field workers across three timezones now submit evidence without a single account being provisioned, and the system that gates real money stays fed.
Before you build another screen
Ask who is on the other side and where they are standing, because a muddy site at 7am is not a desk. Add up what an account really costs across provisioning, training, installation and rotation, and work out who absorbs that cost. Check whether the task is recurring and complex or occasional and simple, since dashboards earn their keep on the first and conversations win the second. And if the structure is not going into a form, be able to say where it is going instead.
The most useful interface decision I made that year was noticing that the right one was already on everybody’s phone.