What we reuse and what stays custom on a fixed-scope build
An honest boundary for fixed-scope engagements: the auth, CI, design-system and infrastructure patterns we reuse, and the domain workflows, pricing rules and RAG corpora that stay custom—without speed-percentage claims.
What we reuse
Type-safe API contracts, preview deploys, auth/RBAC and audit-log scaffolds, dashboard shells, infrastructure baselines, React Native app shells, RAG eval harnesses and design-system primitives—open patterns that shorten setup without locking you into a proprietary framework.
What stays custom
Distributor pricing rules, multi-warehouse count flows, customer-portal permissions, operator workflows and retrieval corpora tied to your SOPs—the work that makes the software yours.
Written into the scope
The reuse/custom split is listed in the statement of work, so change-order risk is visible before kickoff: faster where patterns fit, honest weeks where the domain is new.
A checklist before you compare agencies
Mark your must-haves, data sources, demo cadence and ownership terms before a call. Bring the workflow list (web portal, mobile field app or RAG) and we return a one-page reuse map and a fixed-scope estimate band.
Ready to scope this properly?
Tell us what you are building. A senior engineer replies within one business day with scope, price, and a realistic date — before any contract.