- How is this different from staff augmentation?
- For product development, we coordinate engineering, QA and deployment around agreed deliverables. With staff augmentation, engineers join your team and work under your direction. The proposal defines the responsibilities for the model you choose.
- Can you work inside our codebase and standards?
- Yes. We review your codebase, development standards, access requirements and release process before agreeing on the work. Our work inside Auth0’s product over nine years included components, libraries and extensions.
- Can you work on a system with no tests and no docs?
- We start by tracing the workflows that matter, documenting what the system does and adding tests around the parts we need to change. That review helps us scope the work and identify risks before development.
- What happens to the code when the engagement ends?
- The code we build belongs to you and stays in your repository. We include tests and documentation in the delivery scope and agree on the operating notes and handover needed for your team to maintain it.
- Do we have to start with AI Discovery?
- No. If the work is already defined, we can discuss implementation or adding engineers directly. Discovery helps when you need to decide where AI could help and what would be worth building first.
- How do you price the work?
- We offer fixed-price projects and monthly subscriptions priced on agreed deliverables. Before starting, we define the scope, team, duration, review cadence and how changes or an early end are handled. Staff augmentation has its own agreed roles and engagement terms.
- Can we try working with an engineer first?
- For staff augmentation, the engineer starts with a trial period agreed up front. You pay for that time only if you continue. The proposal sets out the trial length and conditions.