How Long Does It Take to Build a Customer Portal? (And Why 30 Days Is Possible)

If you have asked an agency or development team how long it takes to build a customer portal, you have probably heard the same range: three to six months, sometimes longer. For a mid-market B2B business, that timeline is not just slow. It means another two quarters of your team chasing updates, re-sending documents and fielding "where are we up to?" emails while the project crawls through discovery, design and build.

So when SpotDev says it launches a branded, integrated customer portal in 30 days from contract signing, the reasonable reaction is suspicion. This article explains exactly why that timeline is real, what the 30 days does and does not include, and why we are willing to put a full refund behind it. If you are weighing up the wider decision, the guide to customer portals for mid-market B2B sets the broader context this post sits inside.

Why most portal projects take three to six months

The standard timeline is not a conspiracy. It is the honest output of a particular way of working. Most portal builds start from a blank page. The team runs a long discovery phase, designs screens from scratch, decides on an architecture, builds authentication and permissions ground-up, then wires everything to your systems and tests it. Every one of those steps is invented fresh for your project.

That approach carries two costs: time, and the risk that you do not really know what you are getting until late in the process, which is when scope tends to balloon and dates slip. Three to six months is what it takes to do bespoke work the bespoke way.

Why 30 days is possible: the mechanism

SpotDev hits 30 days because it does not start from a blank page. That is the whole mechanism, and it is worth being specific about, because "we work fast" is not an answer.

• Established portal foundations. Authentication, user management, permissions, the application shell and hosting are already built and proven. We are not reinventing the parts of a portal that are the same in every project.
• Reusable journey patterns. The things your customers actually do in a portal, such as viewing the status of work, downloading documents, submitting requests and self-serving on common questions, follow recognisable patterns. We have built these before. You pick from proven journeys, typically three, rather than designing flows from nothing.
• An in-house engineering team. The people building your portal do this kind of operational software full time. There is no learning curve and no outsourced black box.

Crucially, this is a productised scope on a custom build, not a generic template you are squeezed into. The proven journeys are adapted to your brand, your systems, your data and fields, your permissions, your notifications and your integrations. You get software that fits your business; you just do not pay, in time or money, to rebuild the foundations every B2B portal shares.

The five stages, and where the two weeks comes from

The build runs through five stages from contract to live. Because the foundations and journey patterns already exist, you typically have working software to look at within about two weeks of signing, not a slide deck or a wireframe. That early working version is what makes the rest of the timeline reliable: you are reacting to real software, your feedback is concrete, and there are no surprises waiting at the end. By day 30 the portal is ready for real users, branded and integrated with your systems.

If you want to understand how the integration side works in practice, our integrations work and the guide to connecting systems show how a portal is wired to a CRM as the single source of truth rather than becoming yet another data island.

What the 30 days depends on (your side of the deal)

The timeline is a commitment, but it is not unconditional, and it would be dishonest to pretend otherwise. Thirty days depends on three things:

• A fixed scope. You agree the journeys up front and they do not drift mid-build. This is the single biggest reason most projects slip, and removing it is most of the speed.
• Fast access to the required systems. If the portal needs to read and write to your CRM or other tools, we need credentials and access promptly, not three weeks into the project.
• Prompt feedback. When we put working software in front of you, decisions come back in days, not whenever the next steering meeting happens to fall.

These are not heavy asks, but they are real. A 30-day build is a partnership timeline, and a business that cannot free up a decision-maker for a month is being honest with itself by saying so.

What 30 days does NOT include

The fast timeline works because the scope is deliberately bounded. The fixed price, from £15,000, and the 30-day launch explicitly exclude:

• Open-ended product development, where requirements are still being discovered as you go.
• Complex legacy-system rebuilds.
• Bespoke mobile-app functionality.
• Data-cleansing projects. If your CRM data needs serious remediation first, that is a separate piece of work; our data migration and data engineering teams handle that properly rather than rushing it inside a portal sprint.
• Unlimited integrations. Sensible integrations are in scope; an open-ended list is not.

If you need more than the typical three journeys, extra journeys are £2,000 each and add roughly two days to the timeline. Large additions move you up a tier. The point of naming the exclusions is not to be defensive; it is that a clear boundary is exactly what makes the date hold.

The written guarantee

Here is how we resolve the "too good to be true" objection in practice rather than in prose. If SpotDev misses the agreed launch date, we refund your first payment in full and you keep everything we have built. No clauses, no exclusions. The commercial structure is straightforward: £5,000 on contract signing, the balance before launch, and hosting on Direct Debit or recurring card afterwards.

A guarantee like that only makes sense if the timeline is genuinely repeatable, which is the strongest evidence that the 30-day figure is engineering reality and not a marketing claim. We have built customer portals for clients including Superior, Wolsey Hall Oxford, Icon Solutions and L&DI.

Is a 30-day portal right for you?

This model fits a mid-market B2B services business, in the £3m to £50m revenue and 30 to 500 employee range, where customers, members or partners are constantly chasing your team for updates, documents and status. The whole premise is replacing a "system job" your staff currently do by hand with software your customers run themselves.

It is not the right model for an enterprise that needs 5,000 or more portal users on day one, or for a business that genuinely needs open-ended, exploratory product development.

For most mid-market operators, though, the real question is not whether to build fast but whether to build at all versus buying something off the shelf. That is the next decision to make, and our breakdown of build versus buy for a customer portal is the place to make it. If you want a sense of the figures involved, the guide to custom customer portal cost in the UK covers that side.

When you are ready to scope a build, the customer portals service page sets out the fixed-price, 30-day offer and the guarantee in full.

Frequently asked questions

How long does it really take to build a customer portal?

Built from scratch, most portals take three to six months. SpotDev launches a branded, integrated portal in 30 days from contract signing because it starts from established foundations and reusable journey patterns rather than a blank page. You typically see working software within about two weeks.

Why can SpotDev do in 30 days what others quote three to six months for?

Because the authentication, permissions, application shell and common customer journeys are already built and proven by an in-house engineering team. Your project adapts those proven journeys to your brand, systems, data, permissions and integrations, rather than inventing each piece from scratch. It is a productised scope on a custom build.

What does the 30-day timeline depend on?

Three things: a fixed scope that does not drift, fast access to the systems the portal connects to, and prompt feedback when working software is put in front of you. Miss those and the timeline extends; meet them and 30 days is reliable.

What if you miss the launch date?

SpotDev refunds your first payment in full and you keep everything built. There are no clauses or exclusions on the guarantee.

What is not included in the 30-day fixed price?

Open-ended product development, complex legacy-system rebuilds, bespoke mobile-app functionality, data-cleansing projects and unlimited integrations are all out of scope. Extra journeys are £2,000 each and add about two days; large additions move you to a higher tier.