Questions to Ask a Customer Portal Development Agency (A Buyer's Checklist)

You have decided your customers, members or partners should not have to chase your team for updates, documents and status. The next decision is who builds the portal that replaces that manual work. The agency you pick will shape the cost, the timeline, how it connects to your CRM, and who owns the result. Get the questions wrong and you end up with an open-ended project that drifts, a portal nobody can change after launch, or a stack of integrations that quietly breaks.

This is a buyer's checklist, written for a mid-market B2B operator. Use it on a shortlist call to separate the agencies that have built portals before from the ones that will learn on your budget. If you are still deciding whether to build at all, start with our guide to building versus buying a customer portal, then come back to this when you are choosing a partner.

1. Is it a fixed price, or time and materials?

This is the question that decides how much risk sits with you. Time-and-materials means you pay for hours, the scope is open, and the meter runs until someone calls a halt. Fixed price means the agency has committed to a number and a scope before you sign, which forces them to understand the work up front rather than discover it on your invoice.

Ask directly: what is the price, and what does it cover? A credible answer is specific. For reference, a SpotDev customer portal is fixed-price from £15,000, with extra customer journeys priced at £2,000 each. If an agency cannot give you a number until after a long discovery phase, that is usually a sign the scope is not productised and the cost is not really under control. For a fuller breakdown of where the money goes, read what a custom customer portal costs in the UK.

2. What is the timeline, and what guarantees it?

Any agency can quote a timeline. The useful question is what makes that timeline real. A fast build is not the result of working harder; it is the result of having built the same patterns before.

Ask the mechanism. A SpotDev portal launches in 30 days from contract signing, with working software in roughly two weeks and real users by day 30. That is possible because the foundations are already established, the customer journey patterns are reusable, and the engineering team has built this kind of software many times. You pick proven journeys, typically three, and they are adapted to your brand, systems, data, fields, permissions, notifications and integrations. The speed depends on fixed scope, fast access to your systems and prompt feedback from your side, so ask what they need from you to hit the date.

Then ask the hard follow-up: what happens if you miss it? SpotDev's answer is a written guarantee with no clauses. Miss the agreed launch date and the first payment is refunded in full, and you keep everything built. An agency that will put its fee behind its timeline is telling you something an estimate never can. For more on realistic timelines, see how long it takes to build a customer portal.

3. Who actually builds it, and who supports it afterwards?

Find out whether the people on the sales call are the people who write the code. Some agencies subcontract delivery or hand it to whoever is free that month. An in-house engineering team that has built portals before is the reason a 30-day build is not reckless.

Support matters just as much. Ask what happens after launch: who fixes a bug, who adds a journey, what the hosting and maintenance arrangement looks like, and what it costs. With SpotDev, hosting runs on direct debit or recurring card, and additional journeys can be added later at £2,000 each, taking around two days. You want a clear ongoing relationship, not a project that ends the moment the invoice clears.

4. How will it integrate with our CRM and systems?

A portal that does not talk to your systems is just another place to copy and paste. The whole point is that your customers see live, accurate information, which means the portal has to read from and write to your CRM and the rest of your stack, with your CRM as the single source of truth.

Ask how they handle integration, which systems they have connected before, and how they keep data in sync. This is where a lot of portal projects come unstuck, so it is worth probing. SpotDev's wider work in systems integration and data engineering exists precisely because the portal is only as good as the pipes behind it. If your CRM data is messy, ask whether that is in scope; data cleansing is not part of a fixed portal build, and you may need data migration or a tidy-up first.

5. Who owns the data and the code?

Some platforms lock you in. Your portal lives on their infrastructure, your data sits in their database, and leaving means rebuilding from scratch. Before you sign, get a clear answer on ownership: do you own the code that is built, and can you take your data out cleanly if the relationship ends?

SpotDev's guarantee makes the principle explicit: even if a launch date is missed and the first payment is refunded, you keep everything built. That is the standard to hold any agency to. You are paying for an asset, so make sure it is yours.

6. What is in scope, and what is firmly out?

A productised, fixed-price build works because the boundaries are clear. Ask what is included and, more revealingly, what is not. Vague edges are where budgets and timelines disappear.

SpotDev is explicit that a portal build does not include open-ended product development, complex legacy rebuilds, bespoke mobile-app functionality, data cleansing or unlimited integrations. That clarity is a feature, not a limitation. An agency that pretends everything is included is either underpricing to win the deal or planning to bill you for the gaps later. Map your must-haves against their scope before you commit.

7. Are we actually a good fit for each other?

The best agencies turn down work that will not succeed. A custom portal is a strong fit for a B2B services business where customers, members or partners chase the team for updates, status and documents. It is the wrong tool for an enterprise that needs 5,000-plus portal users from day one, where the requirements look very different.

Ask the agency to describe who they are not a good fit for. A straight answer tells you they understand their own product and will not stretch it to fit your situation badly. If you are not sure whether a portal is the right move, a diagnostic conversation is a sensible first step.

Run the checklist before you sign

Put every shortlisted agency through the same seven questions: pricing model, timeline and what guarantees it, who builds and supports it, integration approach, data and code ownership, scope boundaries, and fit. The answers will sort the agencies that have done this before from the ones that will figure it out on your project.

For the wider context on why mid-market B2B firms are moving to portals in the first place, read our pillar on customer portals for mid-market B2B. When you are ready to see how a fixed-price, 30-day build works in practice, look at the customer portal service and the named clients SpotDev has built for.

Frequently asked questions

Should I choose a fixed-price or time-and-materials portal agency?

For a mid-market B2B build, a fixed price puts the risk of scope and overruns on the agency rather than on you, and it forces them to understand the work before you sign. Time-and-materials keeps the meter running with an open scope. A productised, fixed-price offer, such as SpotDev's from £15,000, is usually the safer commercial position because the number and the scope are agreed up front.

What questions reveal whether an agency can really hit its timeline?

Ask what makes the timeline possible, not just what it is. A credible answer points to established portal foundations, reusable journey patterns and an experienced in-house engineering team, plus what the agency needs from you, such as fast system access and prompt feedback. Then ask what happens if they miss the date. SpotDev, for example, refunds the first payment in full and lets you keep everything built if it misses the agreed launch.

Why does CRM integration matter when choosing a portal agency?

A portal only adds value if it shows live, accurate data, which means it must read from and write to your CRM and other systems with your CRM as the single source of truth. Ask which systems the agency has integrated before and how they keep data in sync. Note that data cleansing and unlimited integrations sit outside a typical fixed-price build, so confirm the boundaries early.

Will I own the portal code and data after it is built?

You should. Ask explicitly whether you own the code and can export your data cleanly if the relationship ends. SpotDev's guarantee makes the principle clear: even if a launch is missed and the first payment is refunded, you keep everything built. Treat that as the standard to hold any agency to, because you are paying for an asset that should be yours.

How do I know if my business is a good fit for a custom portal?

A custom portal suits a B2B services business where customers, members or partners regularly chase your team for updates, status and documents. It is not the right tool for an enterprise needing 5,000-plus users from day one. A good agency will tell you who it is not a fit for; if you are unsure, a diagnostic conversation is a sensible way to test the decision before committing.