Somewhere around your fortieth active client, the shared drive, the WhatsApp group and the email thread stop being a system. Finance is chasing invoice status by screenshot, ops re-sends the same onboarding document four times a month, and someone asks the CTO to "just put a small portal together". That is when the build-or-buy question lands, usually with a two-week deadline and no clear owner.
The first ninety days are about process, not technology
Neither path gives you a working client portal in ninety days; what changes is how much of your internal process gets written down and standardised along the way. Whichever route you take, the first ninety days are mostly spent on decisions: who can see which document, which approvals are mandatory, what counts as "closed". A build forces those decisions into a data model. A buy forces them into configuration screens and, often, workarounds. The portal itself is the easy part, and it is rarely what delays the launch.
Client portal software: build or buy, decided by one question
Buy when your portal needs to do what everyone else's does; build when the portal is part of why clients choose you. Bought portals are genuinely good at the generic jobs — document sharing, ticket trails, invoice downloads, a login page your team does not have to maintain. They get awkward the moment your workflow is unusual: a four-stage quote approval, a GST document set that differs by state, a client who only wants WhatsApp. Build when you can name at least two workflows no off-the-shelf tool will model without a fight.
What the build path costs in days 1-90
A realistic build spends 60-70% of the first ninety days on things no client will ever see. Login, roles and permissions, an audit log, file storage, notification plumbing and a DPDP-compliant consent record all have to exist before the first client logs in. For a portal of moderate complexity, a rough shape looks like this:
- Weeks 1-2: workflow mapping, role matrix, data model
- Weeks 3-5: authentication (magic link or SSO), permissions, audit trail
- Weeks 6-8: document vault, invoice or order data pulled from Tally or your ERP, approval flows
- Weeks 9-11: email and WhatsApp notifications, UAT with five real clients
- Week 12: go-live for one client segment, with a rollback plan
Scope like this sits under our custom software work, and the honest pattern is that week six is when most teams discover the permissions matrix was the real project all along.
What the buy path costs in days 1-90
A bought portal goes live in three to five weeks, and then the first ninety days go into configuration, migration and contract terms. Expect to import client records, remap document folders, re-point notifications and argue about seat counts. Read the contract for three things: how pricing scales per client, what the API actually allows, and how you get your data out. Data residency matters more than vendors admit — under the DPDP Act you are the data fiduciary, so "the vendor handles it" is not a defence. Most buyers also spend four to six weeks on a GST invoicing or WhatsApp integration that the sales deck implied was ready.
A worked example: 40 clients, three workflows
Take a Gurgaon B2B supplier with 40 active accounts and three portal workflows — quote approval, document collection, invoice status. A bought portal at roughly ₹250-600 per client per month costs about ₹1.2-2.9 lakh a year, plus setup and one integration. A custom build of that scope typically runs ₹6-15 lakh with an outside team, plus ₹40-80k a year in hosting and upkeep — comparable to what you would see on our pricing page. On pure cash, buying wins for around three years. The number that usually flips the decision is account-manager time: if the portal recovers six hours a week across the team, that is roughly ₹3-5 lakh a year in loaded cost. We have walked through a few of these trade-offs in our case studies.
Where to start
Before you compare vendors or write a brief, spend one afternoon listing every workflow a client touches, then mark the two you would be embarrassed to run on a competitor's portal. That shortlist, not the feature grid, is the build-or-buy answer. If you want a second opinion on scope and phasing, the Maysan Labs team is happy to sit through it with you — but the list is the real work, and you can start it this week.
Buying software or a website?
Twelve questions to ask any vendor before you sign: price, your data, fit for an Indian business and support.
Get the free checklistRelated case study
Storefront we build and run ourselves
We needed a storefront we could sell and run, not only build: stock, orders, payments and customers in one place.
Written by Sanjay Mandal at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn