Engagement packages
Three ways to engage. Every option comes with fixed pricing, clear scope, and full handover. No surprise bills. No scope creep. No lock-in.
Package
A productized engagement with fixed scope and defined deliverables
- Fixed scope with clear inclusions and exclusions
- Fixed price agreed upfront, no surprises
- Milestone-based delivery
- Full handover, you own all outputs, configs, and deployed components
- 30-day support after launch
Best for: Specific automations, integrations, or feature builds
Discuss Your PackageRetainer
Ongoing engineering capacity for continued builds and support
- Dedicated hours per month
- Flexible scope across builds and maintenance
- Priority response
- Regular strategy and planning sessions
- Unused hours carry forward
Best for: Ongoing development, additional packages, or active support
Explore Retainer OptionsAdvisory
Strategic guidance for teams that need direction, not delivery
- AI readiness and opportunity assessment
- Architecture review and recommendations
- Vendor and technology evaluation
- Team training and upskilling
- On-call technical guidance
Best for: Teams that need to understand the problem before building
Book Advisory CallNo hidden fees. Ever.
The price we quote is the price you pay. We don't charge extra for meetings, reasonable support questions, or revisions that fall within the agreed deliverables. If requirements change or new work is identified, we'll scope and quote it separately before starting, so you always stay in control of costs.
Frequently asked questions
What are your rates?
Package engagements are quoted fixed-price based on scope. Retainer and advisory engagements are priced monthly. We'll give you a number before any work starts, not a range that expands once you've committed.
How long do engagements typically take?
It depends on scope. Focused automations can be delivered in 4–6 weeks. More complex multi-system builds typically run 8–12 weeks. We'll give you a realistic timeline in the scoping conversation, not an optimistic guess.
Who owns the outputs?
You do. All code, configurations, models, and deployed components are yours from day one. We don't retain rights, require ongoing licensing, or lock you into our infrastructure.
Can you work with our existing team?
Yes. We often work alongside client engineers, particularly during the deploy and handover stages. Knowledge transfer is part of every engagement.
What if we're not sure what we need?
Start with a conversation. We offer a free discovery session where we scope the problem, define what a successful outcome looks like, and recommend the right package, or tell you if it's not the right fit.
How do revisions work?
Every package includes defined revision rounds per milestone, typically two. Revisions cover refinements to agreed deliverables, not new requirements or changes in direction. If scope changes, we quote the delta separately before proceeding.
Do you sign NDAs?
Yes, we sign reasonable NDAs before discussing project details.
Ready to talk specifics?
Tell us about your project and we'll put together a custom proposal within 48 hours.
Get a Proposal