Integration Sprint
A bounded implementation for one defined workflow between two systems, including mapping, authentication, reliability controls, logging and production validation.
Definition
A bounded implementation for one defined workflow between two systems, including mapping, authentication, reliability controls, logging and production validation.
Why it matters to the business
It is designed for a known system-to-system transfer where the participants, direction and business action can be bounded.
How it works
Where feasibility, API access, mapping or authentication remain uncertain, the commercial path starts with the $350 Integration Discovery before the $2,000 Sprint is finalized.
Where it appears in real systems
The standard Sprint is $2,000 implementation plus $1,000/month managed maintenance after stabilization; Discovery is credited when the Package Bible rule applies.
Common failure modes
- The operating problem is broader than the written package boundary.
- Required client access or decisions are unavailable.
- New functionality is added without re-scoping.
Implementation considerations
- Confirm standard-package fit before checkout.
- Keep implementation and maintenance boundaries visible.
- Use acceptance criteria before stabilization.
When it is appropriate
Use the Sprint when two systems and one workflow are sufficiently defined; use Discovery first when those technical facts are still uncertain.
When it is not appropriate
Choose another package, discovery or a custom scope when the standard boundary does not fit.
Relationship to BYFORCE
This is the Docs explainer for the Integration Sprint.
Source basis
- docs/commercial/BYFORCE_PACKAGE_BIBLE.md
- docs/website/BYFORCE_SELF_SERVICE_INTAKE_SPEC_2026-09-23.json