Your business doesn't fit in someone else's software
Why small teams should stop bending to their tools, and how AI makes building your own realistic.
Every small business has an email address that doesn't belong to anyone. It's hello@, info@ or bookings@. Clients write to it, suppliers write to it, and the team shares it through forwards, filters and a vague agreement that "someone will answer."
That shared inbox is where the real work of a small business happens. Quotes are requested there, projects change direction there, and invoices get chased there. Yet it's usually the least organised tool the company has.
The shared inbox problem
Email was designed for one person reading their own messages. A shared address breaks that assumption in small, expensive ways:
- Nobody knows who's on it. Two people reply to the same client, or nobody does because everyone assumed someone else had.
- Status lives in people's heads. Is this waiting on the client, or on us? Did we already send the quote? The only way to know is to ask.
- Context gets lost. The call where the client approved the budget, or the detail about which room they booked, never makes it into the thread.
- Replies come from the wrong place. A client writes to hello@yourcompany.com and gets an answer from someone's personal Gmail, because that's where the redirect lands.
None of this is dramatic. It's friction, a little every day, and it adds up.
The usual answer: move everything somewhere else
The standard fix is a helpdesk platform. They're powerful, but they come with a price beyond the monthly fee. You migrate your email, rename everything as "tickets", learn their workflow, pay per seat, and slowly reshape how your team works to match how the software thinks.
For a large support team, that trade makes sense. For a studio of five, a shop, a practice or an agency, it usually doesn't. You end up using 10% of the features while fighting the other 90%.
The tool should adapt to the business, not the other way around.
A different approach: build on top of the email you already have
We ran into this ourselves. Our addresses (hello@ and sound@) redirect into one mailbox, and client conversations kept slipping through. So instead of moving our email anywhere, we built a small tool that sits on top of it.
It connects to the mailbox we already use and reads it. It doesn't replace it. Then it adds the few things a shared inbox is missing:
- Conversations, not piles of messages. Emails are grouped into threads and shown like a chat, with old quoted replies and signatures hidden.
- A status for everything. Each conversation is New, To do, In progress, Waiting, Review or Done. One glance at the sidebar shows what needs attention.
- Private notes. Internal context sits next to the conversation, where the team can see it and the client never does.
- Replies from the right address. If a client wrote to sound@, the reply goes out from sound@, through the right mail server, in the same thread.
- Search that speaks our language. Something like "everything sent to sound@ that isn't done yet" becomes a saved filter, one click away.
Nothing moved. Our email stays in the same place. If we stopped using the tool tomorrow, nothing would be lost.
Where AI changes the equation
A few years ago, building a tool like this for a small team wouldn't have been realistic. Custom software meant long specifications, months of development and a budget only larger companies could justify. So small businesses bought what was on the shelf and adapted.
AI has changed the economics of that decision, mostly through the way it changes the process.
We built this tool in short loops. We'd describe a need in plain language, see a working version, use it with real email, and adjust. The requests were small and very specific to us:
- "Show the status as a pill, and let me change it with the number keys."
- "Replies should come from the address the client wrote to."
- "Move the info column to the left, with the project title at the top."
- "New emails shouldn't have a status yet. Let's call that 'New'."
Some of these changed their minds several times. Our statuses were renamed three times before they felt right. In a traditional project, every one of those changes is a meeting, a ticket and an invoice. With AI as a development partner, each one is a few minutes of iteration, and the tool keeps moving towards how we actually work.
That's the real shift. Prototyping has become almost free, so you can afford to find out what you need by using it, instead of guessing everything up front.
AI speeds things up; judgment is still yours
It would be easy to oversell this, so we won't. AI makes building faster, but it doesn't decide what's worth building, and it doesn't replace care.
A few principles mattered as much as the speed:
- Start from what already works. We built on top of existing email rather than replacing it. Low risk, easy to walk away from.
- Be careful with real data. The tool only reads the mailbox, except when you reply or delete. New features were tested against a fake mail server with made-up messages before touching real client email.
- Keep it small. It does one job. Every feature exists because someone on the team needed it that week.
- Own the result. It runs on our own setup and belongs to us, with no per-seat pricing and no roadmap we don't control.
Custom tools are for small businesses now
The lesson goes well beyond email. Every business has a few processes that off-the-shelf software handles awkwardly: bookings that don't fit a calendar app, quotes that don't fit an invoicing tool, a client pipeline that lives in a spreadsheet nobody quite trusts.
Until recently, the only option was to adapt to the software. Now there's a realistic alternative: small, focused tools built around how your team already works, shaped through quick iteration, and built on the systems you already rely on.
Your business has its own way of working, and that's often what your clients value about you. Your tools should support it, not flatten it.
At Those Kids we design and build custom tools like this for teams who've outgrown spreadsheets but don't want to reshape themselves around generic software. If that sounds familiar, write to us at hello@thosekids.studio. We'll reply from the right address.