Discover
Two weeks inside the business: customers, operations, data, competitive position and the constraints that actually shape the work.
How we work
Six phases from first question to work that holds up.
Every HulkPage engagement, from a technology project to a capability programme to a studio venture, runs through the same operating model. It keeps scope honest, decisions written down and the same senior team accountable from start to scale.
01 / The operating model
Discover · Frame · Design · Build · Launch · Scale.
Frame
A one-page strategic position in plain English. Scope, architecture and success measures signed off before design begins.
Design
Product, system and content decisions tested with real users and operators, not only stakeholders.
Build
Senior engineers shipping production code: typed, tested, observable and secure by design.
Launch
A coordinated release of product, brand, performance and communications against agreed metrics.
Scale
A year-two operating partnership covering growth, capability, product and infrastructure.
01 / Discover · 2 weeks
Discover.
Two weeks inside the business: customers, operations, data, competitive position and the constraints that actually shape the work.
Who is on it — Partner, lead engineer, product lead
- 01Customer and operator interviews
- 02Systems, data and security audit
- 03Competitive and market position
- 04Constraints and risks register
02 / Frame · 1 week
Frame.
A one-page strategic position in plain English. Scope, architecture and success measures signed off before design begins.
Who is on it — Partner with client leadership
- 01One-page strategic position
- 02Scope, architecture and success measures
- 03Delivery plan and commercial terms
- 04Sign-off before design begins
03 / Design · 2–4 weeks
Design.
Product, system and content decisions tested with real users and operators, not only stakeholders.
Who is on it — Product, design and engineering leads
- 01Product and service design
- 02System architecture and data model
- 03Prototypes tested with real users
- 04Content and brand system where needed
04 / Build · 6–16 weeks
Build.
Senior engineers shipping production code: typed, tested, observable and secure by design.
Who is on it — Senior engineering team
- 01Production code: typed, tested, observable
- 02Secure-by-design infrastructure
- 03Integrations with existing systems
- 04Weekly demos against the plan
05 / Launch · 2 weeks
Launch.
A coordinated release of product, brand, performance and communications against agreed metrics.
Who is on it — Full team with client operators
- 01Release and rollout plan
- 02Operator and user enablement
- 03Monitoring, support and escalation
- 04Launch metrics agreed in Frame
06 / Scale · Year two
Scale.
A year-two operating partnership covering growth, capability, product and infrastructure.
Who is on it — Named partner and retained team
- 01Operating partnership
- 02Growth, content and performance
- 03Capability programmes via Hedgre
- 04Infrastructure and product roadmap
07 / Principles
What makes it hold.
Senior on every engagement
There is no junior layer. The people who scope the work are the people who deliver it.
Written before built
Nothing is designed until the one-page position is signed off. Nothing is built until the design is tested.
Measured, not narrated
Every phase ends against metrics agreed in Frame, and we report what actually happened.
Built to be operated
Systems are handed over with the people, documentation and monitoring needed to run them.
“Tell us what you are building. We respond within one business day with a named partner, a clear point of view and a recommendation worth the call.”How every engagement starts
Contact HulkPage