Bring the business bottleneck. OneZero turns it into a defined decision, a reviewable plan, a staged build, evidence, and an operating owner. The process is designed to keep ambition high while making scope, risk, and truth visible.
Every phase should answer a question and earn the next investment.
Discovery earns scope. A prototype earns production. Verification earns release. Handover earns operational confidence. Ongoing work earns renewal by producing useful support, learning, or improvement.
What we will not pretend: A process reduces avoidable risk but cannot guarantee timing, budget, adoption, rankings, leads, revenue, perfect software, vendor availability, or business outcomes.
Choose the right first engagement
Paid discovery or modernization blueprint
Map the customer, workflow, evidence, systems, risk, measures, first release, options, assumptions, and staged roadmap.
Prototype or focused pilot
Test the riskiest user, workflow, technical, content, data, or market assumption before a large production commitment.
Defined production project
Deliver an approved website, campaign system, automation, portal, dashboard, or application with agreed review and acceptance.
What good discovery produces
Discovery is not a long sales call. It produces artifacts that make a decision easier.
- Business outcome, users, buyer or workflow journey, and current-state evidence
- Scope, non-scope, dependencies, assumptions, constraints, and unresolved questions
- Content, data, systems, vendors, access, privacy, security, and specialist requirements
- Prototype or solution approach, milestones, review gates, acceptance, and measures
- Ownership, licences, environments, training, support, maintenance, and handover plan
- Staged estimate or options with the uncertainty and client responsibilities visible
Feedback has a home and a deadline
A named client decision owner consolidates feedback from subject-matter, technical, legal, privacy, marketing, finance, and operating reviewers. Reviewable prototypes and written decisions prevent conflicting messages from becoming silent scope growth.
Change is handled openly
New information may change scope. The team records the request, reason, impact, options, price or timeline effect, and approval before material extra work begins. Small clarifications and genuine defects are distinguished from new features or changed assumptions.
The six OneZero delivery gates
- Diagnose. Understand the business outcome, users, current journey, evidence, systems, pain, constraints, and cost of doing nothing.
- Define. Agree on scope, non-scope, responsibilities, content, data, integrations, controls, measures, acceptance, ownership, and staged plan.
- Design. Make the message, workflow, screens, states, content, and critical interactions reviewable before production hardens them.
- Build. Implement in reviewable increments using approved content, representative test cases, controlled access, and documented decisions.
- Verify and release. Complete agreed functional, content, responsive, accessibility, performance, data, integration, security, and acceptance checks, then launch with a recovery plan.
- Hand over or improve. Transfer the agreed assets, accounts, code, data, documentation, training, and ownership, then continue only where ongoing work has a defined purpose.
Questions buyers usually ask
Do we need paid discovery?
A small defined website or service may not require a separate phase. Custom software, integrations, sensitive data, uncertain product ideas, and multi-stakeholder systems usually benefit from paid discovery before a production price is treated as reliable.
How are revisions handled?
The proposal defines review rounds, decision owners, feedback timing, and acceptance. Material new requirements are assessed as changes rather than hidden inside unlimited revision language.
Can we see work before launch?
Yes. Appropriate projects use drafts, prototypes, staging or test environments, demonstrations, issue records, and acceptance checks before production release.
What happens after launch?
The agreed plan may include warranty, monitoring, maintenance, campaign or SEO optimization, software support, training, reporting, and new releases. Ongoing work is scoped separately from the initial build.
Start with the decision the business needs to make.
Share the current problem, users, systems, evidence, timing, and budget context. OneZero will recommend the smallest engagement that can responsibly move it forward.