METIS LABS
FAQ

Questions, answered in the open.

The things people ask before they reach out: cost, time, ownership, how we measure success, and what happens if software isn't the answer. No sales fog.

What will a project cost?

It starts with a fixed-price proof of concept, quoted upfront, so you risk a known, small amount rather than an open-ended budget. If that proves the idea, the full build is fixed-scope, with the price agreed before we write production code. You always know the number before you commit to it, including what we'd cut to stay inside it.

How much of our time will it take?

About an hour a week on your side: one working demo and one decision moment. We carry the project, so you don't need an internal project manager or a technical lead to babysit it. The aim is to keep you steering without it becoming a second job.

What if software isn't the answer?

Then that's the answer you get, before you've paid for a build. We scope around the problem and what it's costing you, not a feature list. If a process change or an off-the-shelf tool solves it more cheaply, we say so. It costs us a sale and keeps your trust, and we think that's the right trade.

What does "built in the open" mean in practice?

Live access to the repository, a working demo every week, and every significant decision explained in plain language, from day one rather than in a big reveal at the end. You see the work as it happens and steer while steering is still cheap. No black box, no account manager relaying messages.

How do you measure success?

We agree one metric in writing before the first commit: hours saved, errors prevented, turnaround time, whatever the problem is costing you. Then we check the result against it after handover. Progress is measured in your numbers, not in story points or hours billed.

We can't write a technical brief. Is that a problem?

Not at all. The problem in your own words is the brief. Shaping it into something buildable (what hurts, who it hurts, and what would prove it's fixed) is the first thing we do together. You don't need to know what's technically possible; that's our job.

Who owns the code and data?

You do. All of it. The code, the infrastructure and the data are yours, with no license fees to us and no lock-in. When the project ends you're in control, free to continue with us, with someone else, or on your own.

Still wondering?

Ask us the real question.

Tell us the problem and what it's costing you. You'll get a plain-language answer within two business days, including the honest "you don't need custom software" one, if that's the truth.

Open a conversation