How we work
Clear inputs. Clear outputs. Clear finish line.
Before a custom project begins, we agree on the question, the inputs, and what your team will receive. You know what is included, how the review works, and when the handoff is complete.
Fixed scope. Clear documentation. A handoff your team can use.
What to expect
Six commitments that keep the work clear.
-
Start with the right inputs
We agree on the data, access, and decisions needed before delivery starts. The schedule begins when the full input set is available. Incomplete inputs move the start date rather than shorten the work.
-
Agree on the finish line
We define the deliverables and the point at which delivery is complete. Completion is based on that agreed work, not on a future business outcome.
-
Scope follow-on work separately
Recurring updates and additional analysis are not automatically included in a one-time project. Any follow-on work is separately scoped and priced; the agreed review and defect support remain included on their existing terms.
-
Build for handoff
Your team receives the agreed models and logic with documentation explaining the assumptions, calculations, and how to use the work. Day-to-day operation stays with your team.
-
Plan for team availability
Clear input and feedback windows help everyone plan. Changes in your team's availability do not keep the project open indefinitely; the agreed completion, review, and support terms still apply.
-
Be clear about the evidence
We explain what the available information supports and where it falls short. That can mean recommending more history, identifying a limitation, or pointing you toward a simpler option.
The sequence
From the first conversation to handoff.
-
01
Fit Check
We review the question you need to answer, the available data and access, and who can confirm the definitions. If data or technical issues need attention first, we identify them before the project begins.
-
02
Inputs and start date
You provide the agreed input set. Delivery begins when it is complete. Late or partial inputs move the start date rather than compressing the work.
-
03
Delivery and handoff
We define, align, reconcile, validate, and document the work in scope, then hand over the agreed models, logic, and instructions.
-
04
One review round
You have ten business days after delivery to send one consolidated round of feedback on the agreed work.
-
05
Thirty-day logic warranty
The agreed thirty-day logic warranty covers defects where the delivered model does not behave as specified. Requests for Report Pantry to add assumptions, scenarios, plan types, data sources, or business rules beyond the agreed specification are new scope.
-
06
Completion
Delivery is complete at handoff. The ten-business-day feedback window remains available for the agreed review round. If no feedback arrives within that window, the engagement closes under the agreed terms. The review deadline does not shorten the thirty-day logic warranty. New requests outside the agreed work are scoped separately.
Scope
What the engagement covers.
Our focus
- Define the revenue figures and customer lifecycle states in scope.
- Align inconsistent definitions and calculations across the agreed sources.
- Reconcile the figures and document any remaining differences.
- Validate the work and explain what the checks cover.
- Document assumptions, metric ownership, and how definitions are maintained.
- Deliver implementation-ready models and logic your team can use.
Outside the project scope
- Full pipeline rebuilds.
- Ongoing engineering support.
- Unlimited revisions.
- Emergency incident response.
- Ongoing ownership and operation of your forecast.
- An outsourced day-to-day analytics function.
Two different offers
Use the template or build a custom forecast.
The Revenue Forecast Template is a downloadable Excel workbook for one or two subscription plans. You add your inputs and run it yourself, within its documented requirements and limits.
Custom Revenue Forecast is a separately scoped model built around your pricing, plans, and subscriber behavior. We build and document it, then hand it over for your team to run.
Let's find the right starting point.
Tell us what you're trying to understand or improve. We'll help you work out whether Report Pantry is a fit and what a scoped project would involve.