A 1,000-client firm running on memory and chat
Accounting firm · 25 staff · ~1,000 clients worldwide
Dissolved symptoms 1, 2, 3, 4 & 6.
Read the full breakdownMost growing businesses scale until one person becomes the bottleneck — the only one who knows what's happening, what's pending, what comes next. I build the software, automation, and connected systems that lift that weight off you — and I keep them simple enough for your team to actually run.
You're the only one who really knows how everything works.
Your tools — Excel, WhatsApp, email, Tally, your accounting app — don't talk to each other.
You can't see what's happening across the business without asking someone.
Reports are still built by hand, late, every week or month.
Things slip through the cracks — a follow-up missed, an approval stuck, a task dropped.
The information you need — files, documents, history — is scattered and hard to find.
You have the numbers, but you don't fully trust them when it's time to decide.
These aren't seven separate problems. They're symptoms of one — your business depends on people remembering, not on a system.
Accounting, manufacturing, retail — completely different industries. Underneath, the identical problem: the business runs on scattered tools and people's memory, until that becomes the thing holding everyone back. Here's that pattern, solved three ways.
Accounting firm · 25 staff · ~1,000 clients worldwide
Dissolved symptoms 1, 2, 3, 4 & 6.
Read the full breakdownBeauty & wellness retailer · Canada
Twelve stores plus Shopify, and every part spoke a different language: Lightspeed for in-store POS, Shopify online, QuickBooks for accounts, a separate payroll app, even a footfall-counter — none connected. Leadership saw five disconnected apps and stitched the story together by hand.
Brought onto an ERPNext backbone with the existing apps and their data connected in — online, in-store, accounts, and staff finally in one system instead of five islands.
Dissolved symptoms 2, 3 & 7.
Read the full breakdownB2B food-ingredient manufacturer · 3 factories · 200+ staff
Three factories and pan-India sales, run on Excel, Word, WhatsApp and constant phone follow-up — sales chasing price, dispatch and payment by hand. Its most valuable asset, its recipes, sat in laptops, open drives, and a physical locked drawer, with no version control or traceability.
A full discovery first, then one connected system: ERPNext as the operational brain, Zoho CRM for the sales lifecycle, and SharePoint to secure, version and trace the recipes — the crown jewels finally protected like one.
Touched all seven symptoms.
Read the full breakdownThree industries. One pattern.
The tools were already mostly there — they just weren't working as a system.
When something isn't working, the instinct is to go find a better app. A new CRM, a new project tool, another subscription. Most of the time, that's not the problem.
The tools are usually fine. The gap is between them — the CRM doesn't talk to the accounts software, the POS doesn't reach the dashboard, and a person has to sit in the middle copying things across by hand. Adding a sixth tool to five that don't connect doesn't fix that. It just adds a sixth island.
In every project I take on, the first move is rarely new software. It's connecting what's already there into one system, so the business stops depending on someone to bridge the gaps manually — and building something custom only for the few gaps the existing tools genuinely can't cover.
So before you buy another tool, the real question is: what do you already have, and why isn't it working as one system?
For twenty years I've built and fixed business systems for clients around the world — across different roles, industries, and project sizes. For the last five I've done it independently, as SahajViews.
I started on my own because I kept watching the same thing happen. A business would buy software. It would get implemented. The team would use it for a few weeks — then quietly, without anyone deciding to, drift back to their spreadsheets, WhatsApp groups, and email chains. The software hadn't failed technically. It had failed in practice, because the actual work underneath it was never sorted out first.
So I work in a particular order: understand the work, fix the process, then build the system — and I don't call a project done until your team can run it without me.
That order is the whole idea behind the name. Sahaj — simple, effortless. Views — to see clearly. SahajViews means effortless clarity: seeing your business clearly, made simple enough to run on its own.
No pitch, no obligation. Describe what's scattered or manual in your operation,
and I'll tell you straight whether I can help — and whether you even need to build anything.
India, Australia, South Africa, the US, UK & EU