Booking calendar
Pick a slot; the lead is created in the CRM and double bookings are refused.
Case study · oias.in · Labs · Studio · Marketing
oias.in: our own website is our case study
oias.in runs the way we say your operations should. Booking a call writes straight to the CRM, outreach is written by agents within a daily limit a person sets, and the blog is queued and published by a content engine.
See it liveBooking→ CRM, no copy-paste
Agent-runoutreach
Opt-outin every email
The problem
A one-person studio can't spend its day on admin. Every lead, follow-up and post had to happen without someone moving it by hand.
What we built
Outreach engine
A daily job writes a personal email to each queued lead, ramps volume week by week, and never contacts anyone who opted out.
Content engine
Posts are queued and published on schedule.
Founder dashboard
Leads, pipeline and today's priorities on one screen.
How it works
- VisitA buyer reads a page and books a call.
- CaptureThe lead lands in the CRM with the slot.
- Follow upAgents write and send the next step.
- MeetThe founder takes the call.
Decisions that mattered
Humans set the limits
Agents write; volume caps and the opt-out list are set by a person and enforced in code.
Built with
- Static HTML
- Serverless functions
- Zoho CRM
- Vercel
Quick answers
Does OIAS use AI agents to run itself?
Yes. Lead capture, outreach drafting and content publishing on oias.in are run by agents, with limits and approvals set by a person.
Have something like this eating your week?
Talk to OIAS