Work with me
Systems architect · Strategy · AIMumbai · Remote across India

I architect the system. AI builds it. Your business runs on its own.

Rohan KhilareStrategy & AI Automations Head, Shreans Daga FoundationCoach to Indian founders. Builder of systems that keep running after I leave the room.
ROHANKHILARE
particles · move your cursor
Scroll
01 / What I actually do

I'm not the developer. I'm the architect.

I don't come from IT and I don't hand-write code. I do the part that decides whether a system works: the process, the system, and the structure around it. Then I direct AI to build exactly that, test it, and I own the outcome. The same way I coach founders to design a business that runs without them.

PROCESSWhat happens, in what order

Every step a lead, a booking, a rupee or a task takes, mapped before a line of code exists. Mapping is the hard part. Code is the cheap part.

SYSTEMWhat runs it without a person

The automations, the AI agents, the rules enforced on the server. Fifty backend jobs and seventeen CRM workflows came out of this column.

STRUCTUREWho owns what, and how it survives

Roles, decision rights, handoffs, hiring. Written nameless, so it works after anyone leaves. Including me.

Before · April 2026
Everything lived in one person's head
Website rented from an agencyBookings by handReceipts a week lateNo CRMNo role clarityNobody could see where money went
After · September 2026
Systems that run while everyone sleeps
Website owned, team edits itBooking → bed → receipt → CRM, automaticTax receipt in seconds17 CRM workflows5 role documents, hiring toolkitEvery voucher reconciled
⟷
drag the line
The Foundation website, built and owned in-houseWebsite · 35 pages · SEO 100
The retreat booking engineBooking engine · live
Soul Nest guest booking siteHotel system · guest site
Real products.
Live today.
Scroll to unzip
Three of twelve systems. Every screenshot is the live product, captured this week.
02 / Proof in 20 seconds

Don't read about it. Press the button.

A replay of the real booking engine. One click by a guest, six jobs done by the system, zero people. Nothing is charged here. No card form opens.

A Quantum Leap

5-day retreat · Pyramid Valley · 14–18 Oct
Test mode
₹42,000per seat · price read live from the admin panel
Availability live · beds decrement on payment

Demonstration only. No money moves, no card is ever requested. What you'll watch is what happens for a real guest, in order.

booking-engine · cloud functions
1Bed allocated inside a transactionauto
2Payment verified on our server, for the right retreatauto
380G tax receipt generated and sentauto
4Guest added to the CRM, lifecycle taggedauto
5Seat count dropped, everywhereauto
6Confirmation sent on WhatsApp and emailauto
Waiting for the guest…
03 / The systems

Twelve systems. Fly through them.

Scroll to move through the space. Click any card for the problem, the build, the proof and the stack. Six months ago every one was rented, missing, or done by hand.

01/ 12
scroll
04 / Real screens

What the team actually sees.

Not mock-ups. The live products, captured this week. Keep scrolling and the screens change.

WebsiteBooking engineGuest site
Guest site on phone
The website · owned, not rented35 pages the team edits themselves

Rebuilt from scratch, pre-rendered for Google and AI search, images served from the edge. SEO score 100. No agency, no waiting.

The booking engine · takes real moneyPick a plan, pay, get a bed and a tax receipt

Price read live from the admin panel. Payment verified on the server for the right retreat. Beds allocated inside a transaction.

The hotel system · 65 roomsA guest site, a staff console, six phone apps

Front desk, housekeeping, till, kitchen, finance, reports. AI on every screen with the same powers as the badge asking. 713 tests.

05 / Company OS · what I'm building next

A C-suite that runs on your rulebook. You approve. It acts.

One system that holds your business's data, talks to you in plain words, makes the changes and runs the tasks. Not a chatbot. Eight roles, each carrying a rulebook written from the frameworks I coach with, working the way a real leadership team should: one seat does the work, another checks it, and nothing leaves the business until you tap approve.

◐ In build · the engine runs today in demo mode · first customer pilot next · server deployment scripted, not yet live
01Holds your data

One page of truth about the business, a compiled wiki, dated facts that are never deleted, and a search index over every document. An agent gets the eight most relevant pieces, never the whole memory.

02Speaks to you

Talk to the Chair in plain words on your phone. "Chase the leads that went cold." "Write me a Monday brief." It routes the job to the right seat and shows you every hand-off.

03Does the changes

Connected to your CRM, your ads accounts, and any system with an API. Reads happen inside a job. Writes become proposals you approve. Retries never spend twice.

04Acts like a team

Chair, marketing, sales, operations, people, finance, librarian, checker. Maker, then Checker, then you. No seat marks its own work done. Autonomy is earned, never assumed.

The company 8 seats

Talk to the Chair plain words

The brain · knowledge layer · drag to turn
demo · scripted · nothing is sent

The job idle

·Pick a request. The trace shows who did what, in order.

0jobs run
0waited on you
0left the business
₹0est. cost
How it is put together · designed and scripted, one rented server per customer
ONE RENTED SERVER PER CUSTOMER · DOCKER · AUTOMATIC HTTPS · NIGHTLY BACKUPS · KILL SWITCH Your phonetalk · approve The engineChair + 7 seats · 41 job procedures7-step loop: route · plan · do · checkapprove · execute · record · learnGATES ENFORCED IN CODEowner-only approval · daily cost cap · ad cap · idempotency Model gatewayone door for every AI call · budgets · logs Memorythe Company Brief · wikidated facts · search indexdatabase with meaning-search · ledger of every job Connectors · the only way outyour CRM · your ads accounts · any APIreads happen inside a jobwrites become proposals you approveNO APPROVAL RECORD, NO ACTIONoutside results are untrusted data, never instructions
How it improves your decisionsEvery recommendation arrives with the number, the source and the rule it followed. You decide with evidence, not with a feeling.
Decisions wait at the right levelDrafts you just read. Outward actions you approve. Automatic only after thirty days and twenty runs at 95% approval, and never for money.
Nothing is deletedA fact that changes is superseded, not erased. "What was the price in June?" is always answerable. So is "who approved that?"
Built on how I coachThe Chair sets goals the way I set them with founders. Operations runs on process, system, structure. Sales and marketing follow the same playbooks I teach. The team lead reviews every agent monthly.

Honest status: 9 rulebooks, 41 job procedures, 24 role cards and 4 policies are written and red-teamed. The engine runs the seven steps end to end on a laptop in demo mode. The knowledge layer, the clock and the server deployment are next. Customer zero is my current employer. Open the working floor prototype ↗

06 / Outcomes

What changed for the people I work with.

Not what I built. What it did. Each one is live today for a real organisation.

LeadsDM

Enquiries answered in seconds, at midnight, without a person

An AI agent on Instagram, WhatsApp and the website qualifies the lead and hands the hot ones to a human.

Bookings6→0

A guest pays and six things happen with nobody clicking

Bed, payment check, tax receipt, CRM record, seat count, confirmation. What used to be a person, a spreadsheet and a week.

Website0 calls

The team changes its own website the same day, for nothing

No agency, no ticket, no waiting. Twenty-two editing screens they own.

Money28 mo

The founders can finally see which part makes money and which loses it

Every voucher for 28 months reconciled. A "loss" that was really a surplus. A ranked list of what to cut.

Hotel6 apps

A 65-room resort run from six phone apps, with AI on every screen

Front desk, housekeeping, till, kitchen, finance and reports. Staff need zero training.

Team19

Nineteen people pulling toward one 90-day plan

Role clarity for every function, a hiring toolkit, and a team programme delivered in two days.

07 / What it costs, and what it stopped costing

Owned, not rented. Two builds, two price tags.

Two organisations, two sets of numbers. The Foundation's platform replaced rented tools. The hotel system replaced what a vendor or an agency would charge to build. Kept apart on purpose.

₹0

About $20,000 a year of software rent, not paid. CRM, content system, funnel builder, guest app, email monitoring. Five commercial tools priced from their public pages. The Foundation owns the equivalents.

Outside agency
₹0

Gone. They ran the old website. Nothing runs on their servers any more.

Outside developers, ever
₹0

Two complete platforms, 194 commits, one author. What an agency would quote for this is the biggest number on this page, and nobody publishes it.

Automations running
0

50 backend jobs and 17 CRM workflows, counted in the live code and the live account.

₹0

What an agency quotes for a custom operating system of this scope. The market range recorded in the campus operating-system plan, September 2026. The hotel system is the first slice of that build.

Renting a standard hotel system
₹0

Market range for a property system, rising about 10% a year, and it covers only the hotel half. A real vendor quote on file: ₹2.7L a year plus ₹25,000 setup.

A team to build it
₹0

Per role, per year, on published Indian market data: backend, frontend, security, testing, and someone owning how it all talks to each other. Five roles. I covered all five.

What it actually runs on
₹0

One rented server in Bangalore with HTTPS, self-restart and nightly backups. 713 tests. Built in five days. Owned outright.

How the saving actually happens · the same chain every time
1FrameworkDecide what the business is for, who it serves, what to charge. Wrong here and every rupee after is wasted.Saves the money you would spend building the wrong thing.
2OperationsProcess, system, structure. Who owns what, what runs without a person, where work gets dropped.Saves the founder's hours and the second hire you thought you needed.
3MarketingOne engine: positioning, content, lead magnets, funnels, measurement. Every rupee of ad spend traced to a booking.Saves the ad money that was buying the wrong people.
4AutomationOnly now: the CRM workflows, the AI agents, the booking engine, the property system. Built on tools you own.Saves the rent, the agency, and the week of manual work every month.
Worked example · the hotel system, in plain arithmetic

Rent it: a standard property system at ₹2.7 lakh a year plus ₹25,000 setup, and a CRM at ₹1.44 lakh a year plus ₹1.55 lakh setup. Both quotes are on file. That is about ₹4.1 lakh a year, plus ₹1.8 lakh to start, and you still own nothing.

Own it: one rented server at ₹1,584 a month, about ₹19,000 a year. The system, the data and the AI on every screen are yours.

Difference: roughly ₹3.9 lakh a year in rent alone, before counting the ₹1.5 to 4 crore an agency would quote to build the full operating system. That is not a projection. It is subtraction.

₹3.9La year, rent alone+ no build billan agency quote avoided

Sources: vendor quotes on file, the Foundation's own paperwork, the campus operating-system plan, and public pricing pages, all read in September 2026. No figure here is a projection.

08 / The plumbing

HighLevel for the front. n8n for the glue. Code where it matters.

I know where each tool stops. The CRM owns the conversation. n8n moves information between tools. Money and stock go through real code that cannot double-book. Watch one enquiry travel the whole way.

DMInstagram · WhatsApp · webthe enquiry arrives
HLHighLevel CRMcontact, tags, lead score, AI first reply
n8nn8n workflowwebhook → checks → routes the data
fxCloud Functionpayment verified, bed allocated in a transaction
✓Back to the humanreceipt, confirmation, team notified
HighLevel · the CRM and automation backbone

Every contact, every conversation, in one place that follows up by itself.

One AI agent answers on the website, Instagram, Messenger and WhatsApp. Seventeen workflows move each lead from first message to booking to review request. Your sales person sees only the hot ones.

Lead capture & scoreRetreat lifecycleReactivationHot-lead alertReview requestReferral engineAd fast-trackVoice AI callbacks
n8n · self-hosted automation

The glue between your tools.

When a form fills, a sheet updates, a message goes out, a system is told. Ran a live event's bookings. Sends alerts inside the trading system. Ready to connect Company OS to anything with an API.

The rule

Know where the platform stops.

A no-code tool is right for 80%. Allocating beds under concurrent demand needs a transaction. That is real code, and I tell you before you find out the hard way.

Approvals take calendar time

Start them on day one.

A2P registration, WhatsApp template approval, domain authentication, Meta business verification. All run on someone else's clock. Every build plan I write starts with them.

Design the logic, let the owner click

You end up understanding your own system.

Where a platform has no API for building workflows, I write the plain-English spec, the owner builds it, and I verify outcomes through the API. That understanding is worth more than the automation.

09 / The other half

I also coach founders. Same brain, different room.

Where it began

Founders whose business ran on their memory.

Owners of ₹1 to ₹10 crore companies in manufacturing, food, IT, pharma and wellness. Brilliant at the work. Trapped inside it. Nine engagements taught me the same lesson each time: the founder was the system.

DIAGNOSEDESIGNHAND OVER
What I do with you

Find the leak. Design the fix. Hand it over.

A written diagnosis with numbers, not opinions. Then the design: who owns what, what runs without a person, what the founder must decide and what they must stop touching. Six frameworks, one for each thing that breaks as a business grows.

What you keep

A business that runs on process, system and structure. Not on you.

The same design becomes automations, an AI agent, a dashboard, a hiring toolkit. Written nameless, so it survives anyone leaving. Now it also becomes Company OS: the frameworks as a team of AI roles that runs your functions daily and asks you before anything leaves the building.

Owners of ₹1 to ₹10 crore Indian businesses who are stuck because everything depends on them. I help them design a company that runs without them in the room. Six frameworks, each fixing one thing that breaks as a business grows. The same frameworks now sit inside Company OS as rulebooks. Flip them.

01 · Goals & management

The goal system

How a whole team sets goals it can actually hit, and keeps hitting them.

FLIP →
IN PRACTICE

Money goals, function goals and learning goals set together, then three commitments per person. Used to align 19 people to 90-day targets in one session.

02 · Operations

Process · System · Structure

How a business runs without the owner in the room.

FLIP →
IN PRACTICE

Each function defined, designed and developed on all three layers. Five function blueprints and a 13-handoff matrix, where work actually gets dropped.

03 · Team performance

The team engine

How a team performs without being chased.

FLIP →
IN PRACTICE

Aspirations → alignment → analysis → awareness → achievements. A five-piece pack. The session lives or dies in the 48 hours after.

04 · Who to sell to

The customer model

Who your customer really is, what they need, and what to charge.

FLIP →
IN PRACTICE

Segments graded A to D, needs and problems scored, a value number per segment. Turned one ₹24L practice into a ₹1.22cr four-vertical model.

05 · Selling

The sales system

How to sell without ever feeling like a salesman.

FLIP →
IN PRACTICE

A map of every sales conversation, scripts, collateral, a stale-deal rule. And the mindset piece: salespeople are built through rejection, not born.

06 · Nine phases

The marketing engine

From nobody knows you, to nobody can ignore you.

FLIP →
IN PRACTICE

Positioning → content → lead magnets → funnels → measurement. The 66-day retreat calendar came out of it: 10 films, 45 reels, 11 emails.

Case · A coach in Mumbai · Aug 2026

She asked for marketing. The work was structural.

₹24LToday
₹1.22crYear-one model
4Verticals, not 1

Four years practising, seventeen modalities, one product, no entity, no ledger. The diagnosis, said plainly: this is an income, not a business.

Built a 14-section model with 82 tables and an 8-tab workbook with 141 formulas. Named one method instead of seventeen. Repriced the 3-month package from ₹1L to ₹1.75L. Designed 12 funnels, and told her to build the two that cost nothing first.

Capacity did the arguing: the same revenue on 1:1 alone would need 51 clients and 1,440 hours. Arithmetic, not opinion.

Fabric manufactureCurtainsFood manufactureIT servicesPharma D2CWellness practiceCoachingRetreat & hospitalityArt gallery
Patterns / Eight things I see in almost every MSME
01It's an income, not a business+
Revenue is real, but there is no entity, no ledger, no repeatable way to get customers. Marketing is not the constraint.
02The numbers don't reconcile, and everyone builds on them anyway+
Name it as the biggest open question rather than picking a number. A model built on an unreconciled figure is confident and wrong.
03Too many things you're good at, no named method+
Seventeen modalities is a delivery strength and a marketing disaster. Name one method. Everything else becomes what happens inside it.
04Per-session pricing is why clients leave+
It makes every session a re-decision at exactly the moment the work gets uncomfortable. Package pricing with a defined arc.
05Aiming at the output of a decade+
"I want systems like that famous person." That's ten years of audience-building. The sequence is proof → offer → audience → funnel → automation.
06The founder is the constraint+
Every decision gets one test: does this add revenue without adding the founder's hours?
07A structural loss hiding inside a blended P&L+
One function looked survivable in the combined accounts. Isolated, its people cost alone exceeded its income. Insist on per-unit ledgers.
08The 90% ceiling+
Things reach "final 10%" and stay there for weeks. Done means someone other than the builder has used it successfully.
10 / 60-second diagnostic

Where is your business leaking? Six questions.

Answer honestly. You get the pattern I'd look at first, and the one system I'd build before anything else. Nothing is stored.

Question 1 of 6
Your result

Build this first
11 / How I work

Six rules I don't bend.

01

AI proposes. A human approves. The system executes.

The money guardrail in every build, from an ad-spend engine to a trading system to Company OS. Enforced in code, never by convention.

02

Nameless systems survive any departure.

I rejected two drafts that named team members. Function titles only. A process that depends on a person is a person, not a process.

03

Done means someone else used it.

Not 90%. Not "final touches". If nobody but the builder has run it successfully, it's in progress.

04

Own, don't rent.

Every tool you rent is a tool that can hold you hostage. Buy the boring parts. Build the parts that make you different.

05

Map before you build.

A no-code tool is right for 80%. Allocating beds under concurrent demand needs a transaction. I'll tell you where the platform stops before you find out.

06

Measure, don't estimate.

Every figure on this page is counted in live code, read from a live account, or marked as needing input. Nothing is a guess presented as a fact.

The honest column

A record that only lists wins is a marketing document.

  • The first platform still takes test payments. Deliberately: a rehearsal before real money. Three things unblock it, all founder decisions, not code.
  • I chased three inputs daily for two weeks with no escalation path. Now every accountability system I build has one: an item that carries past five days changes owner, forum, or gets killed.
  • Several builds sat at "90% done" for weeks. That's why "done" now has one definition, and it isn't mine to declare.
HighLevelFirebaseCloud FunctionsReactTypeScriptCloudflareRazorpayn8nClaude CodeAnthropic SDKDigitalOceanDockerGA4 · GTM · Meta PixelZerodha KiteWebflowObsidianExcel models
12 / Work with me

Three ways in.

Each one starts with a 30-minute call where I tell you honestly whether I'm the right person, including when I'm not.

Retainer · Most leverage

Fractional Head of Strategy & AI Systems

I sit at your leadership table part-time and own two things: the decisions about what to build, and the building of it.

  • Week 1: find what's broken. A written diagnosis with numbers.
  • Month 1: the first system live and used by someone other than me.
  • Ongoing: a roadmap like the one above, dated, honest.
  • For ₹1–50 crore businesses done renting their capability.
Start with a call
Sprint · Fixed scope

One system in 30 days

You bring the thing that runs on one person's memory. I hand back a system that runs on its own, documented, tested, owned by you.

  • Booking or order flows, CRM automation, AI agents on WhatsApp and Instagram, admin panels, tracking, financial clarity.
  • Built on tools you own. No lock-in, including to me.
  • Handover pack included, with the "looks wrong but is correct" list.
Scope a sprint
Full-time · One company

Head of Strategy & AI Automation

If you need one person who can sit with the founders in the morning and ship the system in the afternoon, I'm open to the right seat.

  • Everything on this page was done in six months, in one role, as one person.
  • I bring my own frameworks, my own second brain, and a working method.
  • Mumbai-based. Remote across India. Travel is fine.
Talk about a role
13 / Results, plainly

Pick what's broken. See what changes, and what I won't promise.

Every line below is something I have already delivered for a real organisation. No revenue projections. No "10×". Just what you will be able to see with your own eyes.

Not promised

What I will never put on a slide.

  • Revenue or profit numbers. They depend on your market, your offer and your team. I'll show you where the leaks are and close them. The upside is yours to measure.
  • A launch date before the map is done. Mapping is the work. Code is the cheap part.
  • "Fully automated" on day one. Autonomy is earned. Every outward action starts with your approval.
14 / Automation studio

Build two automations. Watch them run.

Every automation has the same shape: when something happens, then a chain of things happens on its own. Pick a trigger, pick the steps, choose the channel, press run. Then build a second one. I'll take both from there.

1When… PICK ONE

2Then… PICK UP TO 4, IN ORDER

3Channel

Your blueprint
When something happens, then pick the steps.
0automatic steps
0manual handoffs removed
—built on
your-automation · test run
·Pick a trigger and some steps, then press run.
Idle.
Your automations
Ready to hand over?
Build at least one automation and I'll take it from there.
Send to Rohan on WhatsApp

This opens a WhatsApp message to me with your blueprints. Nothing is stored on this page.

15 / Ask anything

Got a question? Ask my assistant. It only knows what's true.

It answers from the same verified facts as this page, and nothing else. If it doesn't know, it says so and points you to me.

Rohan Khilare

Let's build the thing that runs without you.

ROHAN KHILARESYSTEMS ARCHITECT · STRATEGY & AIMUMBAI

Seven things to try on this page

Each one is a real system or a real decision. Finish all seven and a priority slot opens up.
The reward: a 30-minute working session with me, on your business, ahead of the queue. Unlocks at 7 of 7.
✓