Why I built 1n1.ai (and why I should have done it 2 years ago)

I'm Akram. I live in Vancouver. I run a small software studio called Techalyst. And today I'm shipping the thing I've been quietly working on for the last six months: 1n1.ai, an AI receptionist for small business.

This post is the honest version of how that came together. The genesis was a salon I walked into off Commercial Drive. The technology that makes it actually work didn't exist two years ago. The small businesses that need it most have been waiting for it for at least a decade.

If you came here from the launch link, thanks for reading. If you came here from a search engine because your phone keeps going to voicemail, the short version is at the bottom. The long version is below.

Who 1n1.ai is for

This was always going to be a tool for small business owners. Not enterprise. Not call centers. Not the procurement teams at companies with their own RFP process. The audience I cared about from day one was the salon owner, the dentist, the plumber, the chiropractor, the contractor, the cafe owner. The people who do the work themselves and miss the phone because their hands are full.

The reason was simple. Small business owners are the ones who feel the cost of every missed call. A big company with a call center loses calls and the loss disappears into the spreadsheet. A salon owner loses a call and the next morning her chair is empty for an hour. The pain is direct, daily, and personal.

So the question I started with was: what would actually help these owners? Not what would scale to a billion dollar SaaS. What would make the morning of a single-chair salon better.

The salon visit

In late February I was getting a haircut at a tiny place off Commercial Drive. Two chairs. The owner does cuts on one chair, her stylist friend does colour on the other. Both were busy when I walked in. I waited.

In the twenty minutes I was sitting there, the phone rang four times. The owner picked up the first call, took a booking, hung up, apologized to her client. The next three calls she had to let go. Hands wet, foils in, can't grab the phone without ruining what she was doing. The phone rolled to voicemail every time.

I asked her, while she was washing my hair, "do those people call back?"

She said, "Some do. Most don't. They book the place down the street." She wasn't dramatic about it. Just stating a fact she'd lived with for fifteen years. The lost calls were the cost of doing the job in front of her.

I drove home and didn't think about it for two days. Then on Friday I called a plumber because my dishwasher was flooding. I called five plumbers actually. Voicemail. Voicemail. Voicemail. The fourth one picked up but he was on a job and asked me to call back. The fifth one's voicemail box was full. I ended up paying for an emergency plumber from a national chain who charged me three times the normal rate because they were the only ones who answered.

By Sunday I had the salon owner's voice in my head and the plumber experience in my hands. I started doing the obvious thing: I asked every small business owner I could find, "how do you handle the phone."

What twenty-three owners told me

I talked to twenty-three small business owners over the next three weeks. Salon owners, dentists, plumbers, a roofer, two restaurant owners, a personal trainer, a chiropractor, a real estate agent, three home cleaners, a couple of contractors, a couple of mechanics. Some in Vancouver, some in Burnaby and Richmond, a few in Surrey because that's where my cousin lives and I crashed there for a weekend of conversations.

I asked them the same questions every time:

1. How do you handle inbound calls when you're busy?
2. What does a missed call cost you?
3. Have you ever tried an answering service?
4. Would you pay for something that answered the phone for you?

Almost every owner gave the same shape of answer.

On handling calls: they juggled. The phone went to voicemail. The spouse sometimes answered if they were home. A few had a part-time receptionist for mornings only. Nobody had a clean answer.

On the cost of missed calls: the answer was always higher than I expected. The salon owner figured she lost maybe ten bookings a week to missed calls. At $80 per booking, that's $800 a week. The plumber said his average emergency job was $400 and he probably missed two a week. The roofer just laughed and said "more than my truck payment."

On answering services: half of them had tried one. The complaint was always the same: the service charged $300 to $600 a month, the operators didn't know their pricing or services, the recap emails arrived hours later, and customers complained about the experience. Most had cancelled within six months.

On paying for a better solution: every single one said yes. The price they named was somewhere between $30 and $100 a month. Higher than the cost of a phone line, lower than the cost of a human service. They wanted "something that just answers the phone and sends me the message." That was the entire requirement.

The technical aha

Voice AI in mid-2025 is genuinely different from what it was in 2023. Models like Gemini Flash native audio respond in under a second, handle interruptions naturally, switch languages mid-sentence, and sound human enough that most callers cannot tell. Two years ago the responses were robotic and slow and customers hung up. Now they don't.

I went home from those interviews and started building. The agent had to greet callers in your business name. It had to answer questions from your menu and price list. It had to capture the booking details with the specifics. It had to send the recap email within a minute. It had to handle Cantonese mid-sentence in Burnaby, Punjabi in Surrey, Tagalog in Coquitlam, just like a bilingual receptionist would.

Six months of building later, that's the product. Most of the engineering effort went into the parts that aren't obvious to the user: the call quality, the language handling, the speed of the recap pipeline, the per-number human-first option, the multi-channel agent (same agent answers your phone and your web embed and your mobile app, one configuration). The owner shouldn't have to think about any of that. They should just hear their customer get helped.

What 1n1.ai is

It's an AI receptionist for small business in Canada.

You sign up free. You describe your business in one sentence. You drop in your menu, your pricing sheet, your FAQ, whatever you have. The agent reads them. You pick a voice and a language. You paste a one-line embed on your website and a floating call button appears.

If you want a real phone number, you upgrade to a paid plan and pick one with the area code you want. Customers dial, the agent answers, the recap email arrives within a minute of the call ending. Starts at $32 CAD per month for a small operator with one phone number. Free plan covers the web embed only.

The agent speaks 90+ languages with native accents. It never gets busy because it handles calls in parallel. It works 24/7. If you'd rather try to pick up calls yourself when you can, you can configure a real US or Canada phone number for the agent to ring first, with the AI taking over if no one answers within 15 seconds.

That's the headline product. No demo gatekeeping, no quote process, no annual contract.

I built it through Techalyst, my software studio in Vancouver. Custom integration work (book straight into Mindbody, Square, Jane, Jobber, your own system) is the same team's day job, available to anyone who wants it.

More than answering: what else the same engine can do

The name 1n1.ai came from a simple observation. Every interaction between a customer and a business is fundamentally a one-on-one conversation. A customer dials your salon and talks to you, one-on-one. A receptionist greets a walk-in, one-on-one. A follow-up call after a job, one-on-one. The magic of small business hospitality lives in those one-on-one moments. The AI is built to handle them.

Once the engine is in place, "answering the inbound call" is just the first use case. Small business owners have asked us about:

Scheduled customer check-ins. After a service is done, the agent calls the customer two days later to see how it went, captures the feedback, and emails the owner. Better reviews. Better repeat business. Zero owner effort.

Appointment reminders that talk back. Instead of a one-way SMS, the agent calls the day before, confirms the slot, handles "can I reschedule" requests on the spot, and updates the owner. No more no-shows.

Internal team check-ins. If you have a small crew, the agent runs a weekly one-on-one conversation with each team member, asks what's going well and what isn't, sends the owner a summary. Good for shops with 3 to 15 employees where the owner is also the operator and doesn't have a Monday morning hour to spare.

Lead callbacks. When someone fills in your contact form, the agent calls them within minutes, qualifies the lead, and books a follow-up. Higher conversion than a human callback two hours later.

Outbound surveys. The agent calls a list of past customers (with consent), asks three questions, captures the answers. Better data than email surveys at a fraction of the cost of phone-bank vendors.

We're shipping the inbound receptionist first because that's where the pain is loudest. The rest of the engine is the same. As we build out the scheduling and outbound features, they'll all use the agent you already trained on your business.

The "2 years ago" line

The regret part of the title is real, just not in the way you might expect.

Voice AI was barely good enough for this in late 2024. Maybe early 2024 if you were willing to ship something a little janky. Two years ago the technology wasn't quite ready, but the salon owners and plumbers had been losing calls for fifteen years. Looking back, I wish I'd been having those phone-problem conversations earlier. The product would still have shipped roughly when it did, because the voice tech matters. But the focus, the conviction, the time spent listening to the salon owner with the wet hands and the plumber whose voicemail was full, that I could have started sooner.

The lesson is: go talk to the people. The people will tell you. The longer you wait to listen, the more loss has already happened in the time you were busy building something else.

What's next

The product is at the version that's useful today. The roadmap I care about:

• Scheduling and outbound features rolling out so the same agent that answers your phone can also make the follow-up calls
• More phone number flexibility. Porting existing numbers in, not just buying new ones
• Niche-specific tunings. A salon agent that knows balayage pricing questions, a dental agent that knows cleanings vs root canals, a contractor agent that knows urgent vs scheduled jobs
• Deeper CRM integrations through Techalyst, for the Pro and Business plan customers who want the recaps to land directly in Mindbody, Square, Jane, or whatever system they already use
• More languages. Already at 90+ but always more

What I'm explicitly not doing: turning this into an enterprise platform. Not chasing call centers. Not building a marketplace. The thing that works is small business, simple pricing, fast to set up. I'm going to keep it small business, simple pricing, fast to set up.

If you're reading this

If you're a small business owner and your phone went unanswered today, go to 1n1.ai, sign up free (no card), and have the agent on your website by the end of the afternoon. If it works for you, add a phone number for $32 a month. If it doesn't, no harm done.

If you're a founder reading this for the story: the takeaway is the salon visit. Go to where your hypothetical customers actually work. Watch them for twenty minutes. The product will tell you what it wants to be.

If you're someone I talked to during the twenty-three interviews: thank you. You're the reason this exists in this shape. The roofer, the plumber whose voicemail was full, the salon owners on the Drive and in Surrey, the chiropractor who let me sit in her waiting room for an hour: this is your product. I hope it makes the phone problem smaller, and I hope the scheduling and outbound features arriving over the next few months make even more of the daily grind quieter.

Akram Wahid Vancouver, June 22, 2026