The shop runs on the same firehose

I built Dustav for families. The whole pivot was about a busy parent and the pile of dates they retype by hand. Then I watched a small business run for a week, and realized I'd been describing the same person the whole time.

A shop that lives in its inbox

A shop I know runs its entire operation through email. Every sale rings in as a notification. Every class sign-up arrives as a message. Every supplier order, every refund, every "did this go through?" — email. And at the end of the day, someone sits down and copies the numbers that matter out of those emails into a spreadsheet, by hand, so the books make any sense at all. A fragile little chain of hand-work holding the business together.

That is exactly the parent snapping a photo of the soccer schedule, except it never stops and the stakes are money. The receipts don't come once a season; they come all day. The transcription tax I built Dustav to kill for a household turns out to be a bigger, meaner version of itself inside every small shop.

Same customer, different door

For a while I thought of this as a decision: is Dustav a family product or a business product? Do I have to pick?

I don't, because it was never two products. It's one engine — read the email, do the entry — pointed at two inboxes that hurt in the same way. The family's inbox has school PDFs and party invites and dates that need to land on a calendar. The shop's inbox has receipts and sign-ups and numbers that need to land in a table. Underneath, it's the same job: something arrives in the mess of email, and a person shouldn't have to be the one who copies it out.

The household and the shop are the same customer of the same engine. They just walk in through different doors.

Why setup is a sentence

The reason this can serve a shop and not just a developer is that the setup is a conversation, not a configuration. The tools that already read business email tend to be built for someone technical — a screen of fields to map, a template to define, an integration to wire. A shop owner doesn't have an afternoon for that, and shouldn't need one.

With Dustav you describe the email in a sentence — "save the student, the class, and the amount from my sign-ups" — and it writes the rule for you, then shows you a real row to check. The person who runs the shop can set up the thing that saves them an hour a day, themselves, by talking. That's the whole difference: not that a machine can read the email, but that the person who's drowning in it can put the machine to work without asking anyone for help.

The one-sentence version

I set out to do a family's data entry and accidentally built a small business's back office. Same firehose, same fix: tell it once what to keep, and the inbox files itself — whether the inbox belongs to a household or a shop.