How IndianSMEs work
Before you can build software for a business, you have to be honest about how the business actually runs. This is what we see.
Six patterns, drawn from the businesses we build with. For each: what it looks like, why it's that way, what it costs — and what we built in response. If you run a business in India, you'll recognise most of them.
- 01
WhatsApp is the system of record
What we see
Enquiries, quotes as photos, a thumbs-up as confirmation, payment promises as voice notes, complaints in the same thread weeks later. For a large share of businesses, the order history is a chat history.
Why it's like this
It's where customers are, it works on any phone, and it keeps a record without anyone having to fill in a form. Every attempt to move the business into a formal system competes with a tool that's already winning.
What it costs
The knowledge is there, but nobody can search it, total it, or hand it to a new hire. When one phone is the business, the business is one phone.
What we built for it
FastoSales reads the connected threads, understands a quote or a confirmation in your customers' own phrasing, and writes the structured version into the brain — without asking anyone to change how they talk.
FastoSales - 02
The 60-day receivable is the cash cycle
What we see
B2B customers, especially OEMs and larger buyers, pay on 45, 60, sometimes 90 days. Owners know roughly what's owed; few know exactly, by customer, by age, today.
Why it's like this
Terms are set by the bigger party. Chasing is personal and awkward, so it happens late and inconsistently. The ledger is in the accounting system; the promises are in chat; nobody joins the two.
What it costs
Growth makes cash worse before it makes it better. The single highest-value job in many small businesses is simply knowing who owes what and asking on time.
What we built for it
FastoBooks ages every receivable against the actual invoice, and FastoAnalyst answers "who slipped past 60 days?" in one line. Reminders are drafted on a rhythm you set and wait for your approval before they go.
FastoBooks · FastoAnalyst - 03
The founder is the approval layer
What we see
Payments, discounts, delivery dates, anything to a new party — it goes through the owner, on the phone, often at night. Not because the team can't decide, but because the cost of a wrong call lands on one person.
Why it's like this
In a small business, judgement is the asset. Delegating it without a structure feels like giving it away.
What it costs
The owner is the bottleneck on everything that matters, and the things that matter are mixed in with things that don't. Every decision is a phone call.
What we built for it
Approval rules let you write the judgement down once — above this amount, below list rate, to a new counterparty — and Sentry applies it. Routine completes; consequential waits for a card you can decide in thirty seconds, from your phone. You stay the approver of last resort, not the first.
Sentry · Approvals - 04
The books are in Tally, and the month-end is a week
What we see
Tally or Zoho holds the vouchers. The bank statement arrives separately. Invoices were sent as PDFs or photos from somewhere else. Reconciling them is a monthly event that takes days and ends in GST filing under pressure.
Why it's like this
Three sources, three formats, one person. Most mismatches are timing or partial payment, but every one has to be looked at by hand.
What it costs
Month-end costs the business its most capable person for a week, twelve times a year, and errors in filing are expensive.
What we built for it
FastoBooks connects read-only to the accounting system and the bank, matches what it can, and hands back the handful that need a person — with its best guess at why. Scheduled on the 8th, it turns a week into a report you read.
FastoBooks - 05
The year has a shape, and it isn't the calendar
What we see
October is not September. Diwali, Pongal, the monsoon, the financial year-end, the customer's own plant shutdown — demand, cash and attention move in patterns an owner knows in their bones and no dashboard reflects.
Why it's like this
Most reporting tools were built for a calendar, not a business. They alert on a 30% drop in October that everyone knew was coming.
What it costs
Either the owner ignores the reports, or the reports train the owner to ignore them. Either way, the genuinely new signal gets lost.
What we built for it
The brain carries a compliance and festival calendar for your customer base; Calibra has seen last year's October. FastoAnalyst tells you why a number moved, and says "expected — Diwali" when it is.
FastoAnalyst · Calibra - 06
Knowledge lives in people, not documents
What we see
Which supplier short-pays freight, which customer always asks for a 2% cut, which OEM's buyer is on leave in May — it's known, and it's known by one person. When they're away, the business gets slower.
Why it's like this
Writing it down takes time nobody has, and a document goes stale the week after it's written.
What it costs
The business can't scale past the memory of its key people, and every new hire restarts from zero.
What we built for it
The company brain is the place that knowledge ends up — not because anyone writes it, but because Calibra learns it from completed work. A new agent, or a new employee, starts from what the business already knows.
Company brain · Calibra
See these patterns handled on your own business
Describe your company in a sentence. Watch the brain place it, and the agents pick up the work these patterns describe — receivables, month-end, enquiries.
Hire agents now