The bot maps your journey.The founder maps the bot.
Hatchloom is a one-person studio that builds custom AI support bots for service small businesses — written against the helpdesk, calendar, carrier, SMS provider, and CRM the shop already pays for. Every engagement starts with the same operator-pain problem the rest of the site walks from each angle: the missed reply that lost the enquiry at 11 pm, the FAQ the site content left open, the cart that went cold overnight.
The bot closes those leaks. The work behind the bot is run by the same person who wrote the map and shipped the reply — one inbox, one voice, one operator on the other end.
- Build
- $3k – $5k fixed
- Mode
- Map → build → tune
- Floor
- A 5-min reply
[Founder photo placeholder]
The operator side
[Founder Name]
Solo operator. Built and shipped the bots that map onto the FAQ the site content left open, the reply your team is eating at 11 pm, and the cart that went cold overnight. Same operation as yours, smaller calendar.
Care for fixed-scope rather than subscription-shaped engagements. Care for builds written against the operation as it actually runs, not against a template.
Photo and name are placeholders — the founder's slot. The page renders today so the rest of the site has a face on the other end of the contract.
The origin story
A founder-voice note on the slow reply, the missed question, and the cart that went cold overnight.
Hatchloom started inside vertical small businesses while productizing an AI-first layer for service-side operators — booking, calendar, helpdesk. The shape that kept showing up, on every shop we mapped, was the same: a one- or two-person team whose inbox answered itself only when the team was on the clock, whose FAQ the site content left open, and whose cart-recovery window was unmonitored between 9 pm and 9 am.
The AI side was the easy part. The hard part — and the part the rest of the site walks from each angle — was the map: which FIFO queue holds the thread, which carrier keys the SMS, which CRM reads the customer back the next morning. The engagement exists to write that map in the operator's voice, then ship the bot against it. The same floor every Build quotes inside — and the same worked-loss the pillared pages price against — falls out of that map.
What I kept seeing
- ·The same five-to-seven questions, asked in the same order, missing the same way — answered by hand each time. Real shops rinse through ~100 repeats a month on the same five-row FAQ.
- ·The enquiry that arrived at 11 pm and got a reply at 9 am the next morning — ~1 in 3 across the shops we mapped. The bot "five-minute floor" brings that window down to seconds, not hours.
- ·The cart that went cold overnight because nobody was watching the carrier between 6 pm and 9 am. The same SMS-side bot phones that window back to the morning queue.
The same three leaks the Hatchloom pillars — slow reply, missed questions, cart recovery — walk from each angle. The map catches them; the build closes them. Back to the landing page.
The three lines the engagement runs on
Three lines on a one-person studio — each one keeps the next invoice flat.
The credibility you take away from /about is the same the case studies quietly assume: every Build starts from a map, ships at fixed scope, and only opens a Retainer once the bot has earned its keep.
Picking up where the founder block leaves off
Curious how the engagement shapes up? Two pages, one conversion step.
The page you're reading is the human face on the rest of the site. The pricing page is what the Build actually costs and what lands inside it; the how-it-works page is the three-phase engagement the bot runs through once the map is in hand. If you've met this page and want the substance of the contract, walk either door.
Or jump straight to the case studies if you want the proof before the contract.
One intake away
Got a question the page didn't answer? The founder replies in one business day.
No sales deck, no demo under NDA. Send us the shape of your operation and a window for a 30-minute call, or just write directly to hatchloom-5@polsia.app. We'll tell you in plain English which shape of the engagement fits — and whether the engagement fits at all.
Replies in one business day, usually faster.