Help
Questions we hear most often
Clear answers on scope, ownership, security, pricing, and what happens after kickoff - so you know exactly what you’re buying into.
Help
How do engagements usually start?
Short intro call or async brief: goals, timeline, constraints, and stack. We come back with a proposed shape - squad vs. milestone, rough phases, and what “done” means - before anyone signs anything.
Do you work in our time zone?
We cover multiple zones and align core overlap hours with your team. For urgent issues we define channels and expectations up front so nothing depends on luck.
What tech stacks do you support?
We’re strongest on modern frontend (React, Next.js, React Native, Vue/Nuxt) and the usual ecosystem - TypeScript, GraphQL/REST, design systems, testing, CI. If you’re on something adjacent, we’ll assess honestly in discovery.
How do you price - fixed fee or time & materials?
Both, depending on clarity of scope. MVPs and well-defined milestones often map to fixed phases; evolving roadmaps often use T&M or a retainer with a capped burn. We’ll recommend what reduces risk for your situation.
Who owns the code and IP?
You do - per contract, once invoices are settled. Repos, credentials, and handover are documented so you’re not locked in operationally even if we part ways later.
What about NDAs and security?
We routinely sign NDAs and can align with your security questionnaire and access policies. For regulated domains we follow your rules for data handling, environments, and reviews.
What happens after launch?
That’s up to the roadmap: hypercare, SLAs, backlog grooming, or a lighter maintenance lane. We don’t ghost - we agree on what “steady state” looks like and how we measure it.
We’re mid-project and it’s on fire - can you help?
Often yes. We start with a focused audit: risks, bottlenecks, and a 1–2 week stabilization plan. Rescue work is scoped tightly so you get air cover fast, then decide on a longer partnership.