Working With Us
Last updated: 6 August 2026.
The questions that actually decide whether someone hires a studio, answered before you have to ask them on a call.
Money and contracts
How do you price?
Fixed price against a locked scope. Every productized engagement publishes a budget range and where most projects inside it land — see AI Product Launch, Ops-to-Software Sprint and Product Rescue. After discovery you get one number, not a rate card.
Why not hourly?
Because an hourly rate makes our speed your problem to verify. We work with agents and ship faster than a headcount model implies; billing by the hour would mean charging you less for being better at this, or padding the estimate. Fixed price puts the risk of an overrun on us, which is where it belongs.
What are the payment terms?
Typically 40% to start, 40% at midpoint, 20% on delivery. Invoices are due within 14 days. For Product Rescue, the audit is invoiced separately and credited in full against the build if you proceed.
What if the scope changes mid-project?
Small things get absorbed — we are not going to invoice you for a changed label. Real scope changes get a short written change note with its own price and date impact, agreed before we start on it. Nothing arrives as a surprise line on the final invoice.
What if we want to stop?
You can end an engagement at any point. You pay for the phase in progress, you keep everything produced up to that moment, and we hand over rather than sulk. We have never wanted to keep a client who would rather leave.
Do you take equity instead of fees?
Occasionally, in part, for the right product. It is a conversation, not a discount — ask.
Ownership and rights
Who owns the code?
You do, in full, on payment. Not a licence, not a shared arrangement — assignment of the intellectual property in the deliverables. Work happens in your repository wherever possible, so it is yours as it is written rather than at the end.
What about the things you reuse between clients?
We bring general-purpose tooling, patterns and open-source libraries we already own or that are publicly licensed. Those stay ours and you get a perpetual licence to use them inside the delivered system. We do not take your domain-specific work and resell it to a competitor, and the contract says so.
Can you sign an NDA?
Yes, before a discovery call if you prefer. Send yours or ask for ours.
Can we be a named reference?
Only if you say yes in writing. The case studies on this site are anonymised where confidentiality applies — the three named ones are named because those clients agreed. Silence is a no.
How the work actually runs
Who does the work?
The senior engineer you meet is the senior engineer who builds it. We do not sell you one team and staff you with another. Where an engagement needs a specialist we do not have, we tell you and name them before they touch anything.
Do you subcontract?
Rarely, and never invisibly. Any third party working on your engagement is named in advance and bound by the same confidentiality and data protection terms we are.
You say agents write your code. Who is accountable for it?
A named senior engineer, on every line. Agents write the first pass against tests; a person reads it, owns it, and signs the handover. If something is wrong in production at 2am, "the model wrote it" is not an answer we would accept from ourselves.
How much of our time will this take?
Less than a traditional agency and more than zero. Expect one scoping session, a weekly review of about an hour, and prompt answers to the handful of questions only you can answer. Projects slip when a decision waits three days for a reply, not because engineering is slow.
What do you need from us to start?
A decision-maker who can answer questions, access to the relevant systems, and whatever real data the evaluation needs. That is genuinely it.
Where are you, and does that matter?
Cyprus, working across the EU and beyond. Most engagements run remotely with scheduled calls; on-site is possible where the work genuinely needs it, billed separately.
What time zone do you work in?
EET (UTC+2/+3). That overlaps a full working day with Europe, the morning with the US east coast, and the afternoon with the Gulf and much of Asia.
What language do you work in?
English for all documentation, code and correspondence. Greek is available for conversation where it helps.
After delivery
What happens at handover?
You get the code, the deployment, the documentation, the runbook, and a live walkthrough with whoever will own it next. For AI systems you also get the eval set — quality stays measurable after we leave.
What support is included?
Two weeks of critical-bug support as standard, from the delivery date. That is the window where real usage finds the rough edges.
Can you keep maintaining it?
Yes, on a retainer, or on an ad-hoc basis when you need us. Neither is compulsory — everything is documented so your own developers can take over instead. That is the intended outcome, not a fallback.
What if we want our own team to run it?
Then the handover is aimed at them from the start: conventional stack, documented decisions, and a training session as part of delivery rather than an upsell.
Fit
What do you decline?
Work we would do badly, and work we do not believe in. Specifically: pure staff augmentation, projects where the AI element is decorative, ground-up rewrites sold as quick rescues, and anything where the honest scope does not fit the available budget.
We are not sure whether we need AI at all.
Good instinct. A meaningful share of what looks like an AI problem is a data problem, a process problem, or a two-hundred-line script. We will tell you which, before you have spent anything — it is a faster conversation than you expect.
Is there a minimum project size?
In practice, around €4,000. Below that you want a freelancer, and we will happily say so.
How quickly can you start?
Depends on the queue. Ask, and you will get a real date rather than an optimistic one.
Anything not answered here: [email protected]. We reply within one business day.