Sonnet Code
FAQ

Questions we get a lot.

Answers to what US product teams actually ask when they're evaluating a nearshore engineering partner. If you have a question that isn't here, email us at hello@sonnetcode.com.

What engagement models do you offer?
Three common shapes: staff augmentation (senior engineers embedded in your team, billed weekly), dedicated squads (a self-contained team with a lead, billed monthly), and project-based (fixed scope, fixed price, when the brief is well-defined). We recommend a model after the first call — whichever fits your situation best.
How fast can we start?
Under 48 hours to first kickoff for staff augmentation, and 1–2 weeks to reach steady velocity. Dedicated squads take a few extra days while we line up the right team shape. If a project is urgent we'll tell you honestly whether we can meet the date.
Where is the team based?
Distributed across the Americas. Our engineers work business hours that overlap fully with US Eastern and Central, and the overlap is real — not four scheduled hours a day but the entire workday. Clear written and spoken English is a hiring requirement.
Will you sign an NDA? Can we work under our own contract?
Yes to both. We sign NDAs before discovery calls when you'd like, and we're happy to work under your MSA / SOW templates. If you don't have one we'll send ours — short, plain-English, no weird reverse terms.
Who owns the code and IP?
You do, 100%. Every line of code, design artifact, and piece of documentation we produce under an engagement is your property from the moment it's written. We keep no residual IP claims and sign work-for-hire language where needed.
What's the minimum engagement?
One senior engineer for one month is our floor. Below that the onboarding tax outweighs the output for both sides. For dedicated squads we typically plan in 3-month commitments with month-to-month renewal afterward.
How do you price?
Transparent hourly rates in USD, scaled by seniority. We send a simple rate card on request after the first call. No tier surcharges, no separate "architecture" or "senior review" line items — the engineer you're paying for is the one doing the work.
Can we try before committing long-term?
Yes. A two-week paid pilot on a well-scoped slice of work is a common starting point. If it doesn't click we part ways with no obligation. If it does, we transition into a longer engagement with no re-onboarding cost.
Do you use AI coding tools?
Yes — Claude Code, Cursor, Copilot, and similar are part of how we work. We're transparent about it in every engagement, and we review AI-generated code with the same rigor as human-written code. If your organization has a policy against AI tooling or specific restrictions (e.g. no code leaving your VPC), we'll honor them.
Do you work weekends or offer 24/7 support?
Standard engagements run business days only. For on-call rotations or after-hours incident response we can set that up explicitly in the SOW — priced separately so you know what you're paying for.

Still have questions? Fifteen minutes on a call usually covers them all.