Five stages. Six weeks. One accountable team.
Every project moves through the same sequence. You get a working staging build every week, not a slide deck, and a team that stays on after launch.
01— The sequenceFive stages
The same five stages, every time.
A typical Portal Build runs about six weeks. Smaller projects compress the stages; larger ones add weeks to Build and Integrate, never skip a stage.
Week 101
Discover Systems audit
We map how work moves today: the people, the tools, the data, and the places things get stuck. Most schedule risk is removed here, before anything is built.
You receive
- Audit summary and agreed scope
- Risk and dependency list
- Project plan with weekly milestones
We need from you
- A decision-maker and one day-to-day contact
- Access to the systems or examples we are replacing or connecting
- Your definition of success
Week 202
Design Architecture & interface
Information architecture and interface design are reviewed together, so the structure underneath and the screens on top agree. Roles, data model and key flows are settled on paper first.
You receive
- Information architecture and role map
- Key screens and a component kit
- Architecture diagram: data model and integrations
We need from you
- Feedback inside the agreed review window
- Brand assets, if you have them
Weeks 3 to 403
Build Development sprints
We build in weekly sprints against a working staging environment, so you review the real thing every week, not slides.
You receive
- A live staging site, updated weekly
- A short written note after each demo
- Automated tests on the critical paths
We need from you
- Someone at each weekly demo
- Content and sample data when we ask for it
Week 504
Integrate Connect and verify
CRM, billing, single sign-on and any other systems are connected and tested end to end, with a dry run of the data migration before launch.
You receive
- Working integrations with failure alerts
- Migration dry-run results
- Security and access review
We need from you
- Sandbox or API access for each system
- Sign-off on the migrated sample data
Week 6 onward05
Operate Launch & support
We launch against a checklist, then stay on: monitoring, backups and an SLA-backed support line from the first day of real traffic.
You receive
- Production launch with a rollback plan
- Monitoring, alerts and tested backups
- Handover documentation and runbooks
We need from you
- A named owner for ongoing requests
02— How we workFour habits
Small habits that prevent big surprises.
01Weekly demos, not decks
You see working software every week, on a staging site you can click through.
02One accountable lead
A single person answers for scope, schedule and quality.
03Decisions in writing
Scope changes and key decisions are written down and agreed, so nothing is remembered differently later.
04Built to be handed over
Documentation and runbooks mean your team is never dependent on ours.
Next step
Start with a systems audit.
Send us a few lines about what you are running into. Week one is where we find out whether it is a site, a portal, or something in between.