A commercial model should match what is known.
Compare Hazina's fixed-scope build, product partnership and operate-and-improve models. Every price follows a reviewed scope and written quote.
01
Fixed-scope build
A defined problem, bounded release and written acceptance criteria.
Best for: A clear initial system or release with accountable reviewers and stable boundaries.
Commercial basis
Quoted after scoping
Included
- • Discovery and scope record
- • Design and engineering
- • Verification and agreed handover
Separate or excluded
- • Unbounded feature changes
- • Third-party charges
- • Ongoing operation unless quoted
02
Product partnership
A continuing build relationship for a product whose priorities will change as evidence arrives.
Best for: Founders and product owners who need discovery, delivery and prioritization to remain connected.
Commercial basis
Quoted after scoping
Included
- • Product and technical planning
- • Reviewed delivery slices
- • Operating backlog and decision records
Separate or excluded
- • Guaranteed market outcomes
- • Unlimited simultaneous priorities
- • Unverified provider costs
03
Operate and improve
A retainer for an agreed support boundary, controlled changes and a prioritized operating backlog.
Best for: Live systems that need accountable upkeep and deliberate improvement after release.
Commercial basis
Quoted after scoping
Included
- • Agreed support boundary
- • Prioritized maintenance and improvements
- • Release and change records
Separate or excluded
- • Unspecified around-the-clock support
- • Third-party service charges
- • Major new products outside the retainer boundary
What shapes the quote
Complexity belongs in the scope, not a surprise invoice.
- 01Number and risk of critical workflows
- 02Roles, approval boundaries and record complexity
- 03Migration quality and reconciliation work
- 04Offline, device and integration requirements
- 05Security, verification and operating obligations
Third parties
Infrastructure, provider and usage charges are identified separately after requirements are known.
Scope changes
A change is recorded with its effect on acceptance, risk, cost and sequence before work proceeds.
Ownership and handover
The written proposal and agreement state the ownership, access and handover boundary. Unverified policy is not implied here.
From brief to written quote
- 01
Share the current process
- 02
Agree the system boundary
- 03
Receive a written scope and quote
Questions
Commercial questions
Why are there no public prices?
The cost depends on workflow risk, records, roles, migration, integrations and operating responsibility. Publishing an unsupported number would be less useful than a written scope.
Are third-party services included?
Provider, infrastructure and usage charges are identified separately in the written quote when their requirements are known.
What happens when scope changes?
The effect on acceptance criteria, risk, cost and sequence is recorded before the changed work is accepted.
Who owns the finished work?
Ownership and handover terms are stated in the written proposal and agreement. Public policy details remain unpublished until formally verified.
Next record
Get a written quote grounded in the work.
We start by reviewing the process and confirming fit. If the work is clear, the next step is a written scope and quote.