FAQ
Frequently asked questions
Straight answers. No sales talk.
How do you price engagements?
We don't publish rates. Every engagement is scoped against your specific constraints — latency, audit requirements, team size, timeline. The scope estimator on our home page gives a directional sense of complexity. After a call, we'll send a written scope within a week.
What's the minimum engagement?
Architecture advisory starts at 2 weeks. For build work, we typically look at 6+ weeks to do anything worth doing. We're not a good fit for "just fix this one bug" — there are better firms for that kind of work.
Can you work with our existing codebase?
Yes. We modernize legacy systems with the strangler fig pattern — facade in front, replace slice by slice, parity tests throughout. Big-bang rewrites are almost always the wrong answer. Almost.
Do you do fixed-price or time-and-materials?
Fixed-scope, fixed-price. We quote a number, you know the budget. No billable hours, no surprise invoices. If scope changes materially, we revisit the quote together.
How big is the team?
12 engineers. We stay small on purpose. Every person has shipped production systems at scale. We don't hire for potential — we hire for proof. For most engagements, 2-4 engineers are embedded with your team.
What industries do you work in?
We work wherever the technical problems are hard. Fintech, logistics, healthcare, marketplaces, developer tools. We don't specialize by industry — we specialize by complexity. If your system needs to be reliable, secure, and fast, we're probably a fit.
Do you sign NDAs?
Of course. But we also publish representative case studies with composited details. If you want to see our work before engaging, we'll show you. We're proud of what we've built.
What happens after the build?
We stay through the first real traffic, not just the launch. After handoff, we offer an advisory retainer for ongoing architecture review. Most clients use it for 3-6 months, then don't need it anymore.
Do you work with startups or only enterprises?
Both. If the technical problem is genuinely hard, the company size doesn't matter. We've built systems for 5-person startups and 500-person enterprises. The common thread is: conventional tools stopped working.
What's your tech stack?
Rust, Go, TypeScript, Python for application code. PostgreSQL, Redis, Kafka for data. Kubernetes, Terraform for infra. We reach for the right tool, not the trendy one. See the full stack on our home page.
How fast can you start?
Usually within 2 weeks of signing. We keep a small reserve for urgent engagements. If something is genuinely on fire, tell us on the call and we'll see what we can do.
What if the work is outside your range?
We'll tell you on the first call. We'd rather refer you to a better fit than take on work we can't do well. Our reputation matters more than any single engagement.
Still have questions?
Use the contact form or book a call. We answer within two business days.
Book a call