Listen usually one to two weeks
Interviews with the people who send requests and the people who fulfil them. We collect real examples and current statuses, and walk through each step of a typical request. Output: a written current-state map and a list of the decisions the portal must support.
Shape usually two to three weeks
A clickable prototype of the primary journeys, tested with three to five real users from your side. A scope document with in, out and unknown, an integration check against your actual systems and a cost range. Output: prototype, scope, fixed price or time-and-materials proposal for the build.
Build scoped per project
Fortnightly releases to a staging site. A short review call after each release. Automated tests on the parts that move money or data between systems. Accessibility checks with keyboard and screen reader as we go, not at the end. Output: working software you can use while it is built.
Hand over one to two weeks
Production launch with a rollback plan, admin training, customer help text, documentation and a walkthrough of the code for your developers or a future supplier. Output: everything needed to run the portal without us.
How we price
Listen and Shape are priced as fixed packages agreed in advance. Build is either a fixed price against the agreed scope or a monthly team rate, depending on how settled the scope is. We explain which suits your situation and why. Support after launch is a separate, optional arrangement, described on the help desk page.
What slows projects down
Unavailable decision-makers, test access arriving late, and scope changes that are not written down. We will flag each one as soon as it appears, with the effect on time and cost.