How do you actually price a project? 01
Per case, and you get the number before you commit to anything. Most of what reaches us now is a hard problem in the six figures — that is a description of our inbox, not a floor. We have taken much smaller projects and will again. What actually moves the number is latitude, not size: a brief that leaves us room to decide how the thing should work is a different job from one that is already specified down to the last screen, and we price it differently. Some of the work we are proudest of came in well under our usual rate because we were trusted to make the calls. Mechanically: builds are scoped in two-week sprints at a fixed senior-team rate, never hourly; products move to a retainer or revenue-share once telemetry lands. Tell us the problem and the budget you have — if it is not a fit you will hear it on the first call, not after a proposal.
How long does a typical engagement take? 02
A focused build runs 6–14 weeks from kickoff to launch. Discovery + Define is the first 2–3 weeks; you can stop after that with a deliverable in hand. We don't do open-ended retainers without a roadmap.
Who actually does the work? 03
The senior engineers and designers you meet on the first call. No hand-off to juniors, no offshore subcontracting, no agency-bait-and-switch. Small team by design.
Do you work outside Portugal? 04
Yes — we ship for clients across the EU, UK, US and the Gulf. The studio is fully remote with team across Leiria & Lisboa; the work happens wherever it has to. Async-friendly, weekly demos, on-site when it matters.
Will you NDA / IP-assign upfront? 05
Always. Mutual NDA before the first call if needed, full IP assignment on delivery as standard. We never reuse client code or designs across engagements.
Can you take over an existing build? 06
Yes. We've inherited stacks from agencies, freelancers and ex-CTOs. We diligence first (1-week paid audit), then propose a stabilise-then-ship plan with a clear hand-off path back to your team if you want one.
What technologies do you work with? 07
Backend: Node, Python, PHP, Go. Frontend: React, Next.js, Vue, native Swift/Kotlin. 3D / VR: Unity, Unreal, WebGL, Three.js, Matterport. We pick the stack that fits the problem, not the trend cycle.
What happens after launch? 08
You can take it in-house, or stay on a retainer for telemetry, iteration, content and paid acquisition. Either way, you get full source, full ownership and full documentation. No vendor lock-in.
How do you handle data, privacy and GDPR? 09
We're a Portuguese company subject to EU GDPR. All client data stays in EU regions, encrypted at rest and in transit. We sign DPAs on request and run privacy reviews before launch on every consumer-facing build.
What's the smallest project you'll take? 10
A single sprint — typically a focused prototype, brand refresh or technical audit. We don't do hourly billing.
Do you work with non-tech founders? 11
Often. Half our clients can't read code. We translate technical decisions into business consequences and document everything so you can hand it to your next CTO without a migration project.
When are you the wrong studio? 12
When you want the cheapest quote — we bill a fixed senior-team rate, never by the hour, and we are rarely the lowest number. When you need a body-shop to execute a spec somebody else wrote; we argue about the problem first, and if the brief is wrong we will say so. When the work is a one-off asset with no product behind it — a single banner, a logo on its own, a landing page for a campaign that ends in three weeks. When you need a team of twenty by Monday: we are three senior people by design and we do not subcontract the work out to strangers. And when the decision has already been made and what you want is someone to agree with it.
