Technical & engagement FAQs
Questions worth answering before the first call.
Straight answers on intellectual property, the stack, pricing and how the practice works alongside founders and in-house developers.
Before contacting
Ownership, stack, pricing and handover.
Who owns the source code, IP and cloud accounts?
You own all source code, documentation, diagrams and intellectual property on milestone payment. Work happens inside your own GitHub or GitLab repositories and your own AWS or Cloudflare accounts from day one, so you always keep full administrative control.
Which technology stack do you work in?
Day to day: Go, Python and TypeScript services on Postgres, with Terraform, containers, AWS and Cloudflare Workers. Existing Ruby on Rails, Django and older REST or SOAP systems are regularly audited and modernised too.
Do you bill hourly or by fixed milestones?
Audits, discovery sprints and clearly defined builds are fixed-fee, split into milestone deliverables so the budget cannot balloon. Fractional principal engineering is a flat monthly retainer. Nothing is collected on this site; invoices go out on milestones, net fifteen.
Can you work alongside our in-house developers?
Yes. Most scopes run with your engineers reviewing, and pairing sessions can be written in. The work joins your existing Slack, Linear or Jira and Git workflow: architecture RFCs, pull-request reviews and steadier velocity without stepping on toes.
What if we have no finished specs yet?
That is what the two-week discovery sprint is for. Your workflow becomes user flows, entity-relationship models, API contracts and milestone specs before you commit to a full build.
How are testing and security handled?
Unit and integration tests, CI linting and type checks, and OWASP hygiene (parameterised queries, strict auth validation, encrypted secrets) are part of every milestone, never an afterthought after launch.
What happens after launch?
Every build ships with operational runbooks, live handover training and a complimentary 30-day warranty covering defects within the agreed scope. Ongoing feature work or infrastructure stewardship can continue on a light monthly retainer.
Will you sign an NDA before reviewing our repository?
Yes. Mutual NDAs are routine before audits, due-diligence reviews and discovery calls. Send the outline through the contact form, never credentials or access tokens, and expect a reply within two working days.