custom software & ai automation for businesses.
i build the tools your team actually runs on.
automation, ai, internal tools, crms.
building in public.
wrote up why i built this.
56% of us leisure travellers used ai for a trip. only 8% said the ai answer alone was enough. most click through to the company to check.
so they land on the tour operator's site with a route already in mind. and find a contact form.
full write-up 👇
looked at tour agency sites in uzbekistan. none of the ones i checked had an ai assistant.
so i built one. it answers in english, uzbek and russian, gives exact prices from the agency's own tours, and turns the chat into a booking request.
25 test chats, 0 made-up prices.
@ZenModeJon not yet from x. our leads so far came from searching linkedin posts where people ask for a developer. x has been better for meeting builders than clients.
looked at tour agency sites in uzbekistan. none of the ones i checked had an ai assistant.
so i built one. it answers in english, uzbek and russian, gives exact prices from the agency's own tours, and turns the chat into a booking request.
25 test chats, 0 made-up prices.
most small businesses don't need another app. they need the ones they already have to talk: orders in one place, payments in another, the schedule in a sheet, and someone copying between them every evening. what's the copy-paste job your team does every day?
@ShawnGrantTC the cheap fix is a short voice note per building: the tech walks it once, talks through shutoffs and quirks, it gets transcribed and tagged by location. an hour of walking beats a binder nobody updates.
added an ai sales assistant to aviago's telegram bot (a tour operator). the useful part isn't the ai answering, it's knowing when not to: anything it shouldn't decide alone goes to a human with the context summed up, so the customer never repeats themselves.
@JustinDevonshi1 the hardest part is usually what lives only in the owner's head: who's booked, who paid, who needs a follow-up. once that sits in one simple system, stepping back gets a lot easier.
@ShawnGrantTC both. the acknowledge vs resolve split is the useful part. most owners only see resolve, so a ticket can sit unseen for hours and still look fine on paper.
the long version of how i prepare before pitching a business i've never worked with: where the industry makes and loses money, where work waits, the owner's morning numbers, then a clickable demo. link below
before pitching a business i've never worked with:
1. learn how their industry makes and loses money
2. map who does what and where work waits
3. find the numbers the owner checks every morning
4. build a clickable demo around them
5. walk them through their own day in it
what's one thing your team still tracks in a spreadsheet that you know shouldn't be there?
orders, stock, payments, who's doing what?
asking because that's usually where i'd start building.
most devs pitch with slides and a price.
before the deal, i study how the client's industry works and show them a clickable demo of their own system.
they see i understand their business before they pay anything.
next few days: an outdoor ad agency, a pharma holding, a roofer.
built rasmfolio for a friend who keeps a photo diary on telegram.
the channel is the cms. he posts a frame there, and every night it lands on the site in the same order, with the same caption.
150+ frames, 10 series, uzbek and english.
https://t.co/ymNyWExt7i