Put a number around the work. Before the work begins.
Choose how often you want Gizzada beside the organization, how much parallel capacity the work needs, and how long the engagement should run. The same inputs always produce the same planning estimate.
A transparent planning instrument—not a binding quote.
Configure the working rhythm.
These are delivery inputs, not company-size labels. Start with the rhythm the problem needs; Gizzada will confirm scope with you before anything is agreed.
Same inputs, same rule. Use this when the engagement changes rhythm partway through — a fortnight on site, then a day a month to hold the new way of working.
Calculated using a four-week planning month. Platform, third-party and separately scoped costs are not included.
One phase. Add another when the rhythm changes partway through.
Each week is priced at the monthly rate for that cadence divided by the four-week planning month.
No hidden scoring. Three visible inputs.
One weekly day with one two-person team is the base unit. Parallel teams scale linearly. A more concentrated weekly cadence carries a stated intensity factor because the same planning and adoption work must move faster.
Engagement total = monthly estimate × term in months. One week = monthly estimate ÷ 4, the planning month — which is how a phased engagement prices each stretch on its own rhythm without changing the rule. A phase running once or twice a month is priced by its days at the one-day-a-week rate.
People who study, shape and deploy beside you.
The unit is time and capacity; the work inside it remains cross-disciplinary. We use the instruments the organization actually needs, whether they are ours, yours, or a trusted third party’s.
Study the work
Observe the real process, speak with its owners and make the friction visible before prescribing a system.
Shape the move
Agree the better rhythm, its measures, the instruments people need and the boundary of the engagement.
Deploy beside people
Design, integrate, build and adapt in the operating environment—not from a hand-off document at a distance.
Leave a working record
Document decisions, process changes, evidence and the forward roadmap so the organization keeps what it learned.
What is inside the estimate—and what remains separate.
Transparency means showing the edge as clearly as the number. The estimate covers Gizzada’s professional time for the agreed engagement and cadence.
A one-off working visit for a specific problem that does not need a standing engagement.
- The agreed two-person team capacity
- Study, solution shaping and deployment work
- Working sessions with the people who own the process
- Implementation record and forward roadmap
- Correction of bugs in what Gizzada agreed to deliver
- Declared roadmap items when they become available
- Platform subscriptions and ongoing operating fees
- Third-party software, services, hardware or equipment
- Taxes and travel outside the agreed base
- Data remediation outside the agreed engagement
- Enhancements not on the declared roadmap
- Customer-specific builds beyond the agreed boundary
Every new request has a known home.
Agreeing these four categories early protects the client relationship. A correction is not treated like new scope, and new scope is not smuggled in as a correction.
Bug
It does not do what we agreed it would do. Gizzada corrects it.
No additional chargeDeclared roadmap
It is already planned. We tell you where it sits and when to expect it.
No additional chargeEnhancement
It is useful but not on the declared roadmap. We scope, price and date it.
Quoted separatelyCustom build
It is specific to your organization. We define it as its own piece of work.
Quoted separatelyBring us the process that keeps costing attention.
We will study the situation, confirm the smallest honest boundary, and put the scope, cadence and price in writing.