Skip to main content

Frequently Asked Questions

Common questions about how we work — scope changes, IP ownership, stacks, post-handoff support, warranty, NDAs, and in-house teams.

Frequently Asked Questions

Common questions about how we work, what’s included, and what happens after delivery.

What if scope changes mid-build?

We re-scope in writing with a new fixed quote for the delta — you approve before any work happens. The original scope’s price stays the price; we don’t run a meter.

Who owns the data and IP?

You do — all of it, including prompts, fine-tunes, and any generated assets. We don’t train on your data, and we don’t reuse it across engagements.

What languages and stacks do you work in?

TypeScript by default. PHP, Ruby, Python, and .NET when your team already runs on one of them — we pick for your team’s reality, not our house preference.

What support do I get after handoff?

A 30-day defect window is included — bugs we caused, we fix, free. Day 31 isn’t the end of the relationship — it’s just no longer billable by default.

Is there a warranty beyond the 30-day window?

The defect window covers what we shipped, no extension by default. Extended maintenance — feature sprints, observability audits, LLM add-ons — is available as a scoped sprint, never a standing retainer.

Will you sign an NDA?

Yes — mutual NDAs, standard template, about a day to turn around. Happy to use yours if you have one.

What if we already have in-house engineers?

Even better. We build in the open, in your stack, and the handoff includes pairing time so your team can run with the repo from day one.

Can I cancel late in the build?

Yes. You pay for work to the last approved milestone and keep that code. Fixed price means no penalty padding — and no retainer to unwind.

Still have questions?

Ask a question or request a quote — we read everything that comes in.