Do you need technical skills to work with Figue?

No. You describe what you want to achieve, not how to code it. You approve on a preview, using the product the way your customers do. Technical choices are explained in plain words when they affect you: a cost, a timeline, a risk.

Our product was built with AI or no-code, without a developer. Is that a problem?

No, it is a common starting point. The first request is often an assessment: what holds, what is fragile, what is a security risk. Then we fix things in the order you choose. If everything needs rebuilding, we tell you: a fixed-price project is then the better fit.

Does Figue replace a CTO?

Not entirely. The team does the work of a tech team: scoping, building, reviewing, testing, shipping, and flagging risks to you. Priorities and product trade-offs stay yours. If you are looking for a partner who carries the technical vision with you, that is a hire or a co-founder.

What if I hire a CTO later?

The subscription has no commitment and stops at the end of the period. The code is yours, transferred as paid work is delivered, in a repository you have access to. Your future CTO picks up a product that belongs to you, with the history of every request.

UNLIMITED DEVELOPMENT FOR FOUNDERS

Non-technical founder, no CTO? Your product still ships.

IN TWO SENTENCES

For a non-technical founder with no CTO, Figue Unlimited acts as your tech team: engineers keep your product moving, whether it started with a freelancer, an agency, no-code or AI. You keep the priorities, without hiring or managing developers.

Unlimited development, explained

What do you ask for when you have no CTO?

What you ask for.

You talk about outcomes, the team handles the how. Here is what founders without a CTO ask for most often.

Take over a vendor’s code

The freelancer or agency has left. We read, document and take over.

Harden an AI-built product

What AI generated, reviewed, secured, and put live properly.

Get past a no-code limit

The feature the no-code tool cannot do, built alongside it.

Ship the next feature

The one your customers keep asking for, scoped with you before it is built.

Fix what breaks

The bug a customer reported, reproduced, fixed, checked.

Plug in payments or a tool

Stripe, a CRM, an email tool, e-signature.

Get an assessment

A written view of the code, the risks, and what to deal with first.

Measure usage

The metrics that matter to you, in a simple dashboard.

How do you run a product without being technical?

You ask. We build. You approve.

One active request at a time per slot. The queue has no limit, and you set its order.

01
You ask
In writing, by voice, or from Claude or ChatGPT through MCP. In your own words, no specification needed.
02
We scope
The team asks the useful questions, sets the scope and splits the work into shippable steps.
03
One request at a time
An engineer builds the top of your queue, with AI to speed things up and a human review.
04
You approve
You test on a preview. Once approved, the delivery goes to production.
05
On to the next one
In the order you chose. A request waiting on your answer does not block the slot.

Which founders is it for?

Made for you, or not.

Yes, if

Your product exists, it has users, and you have no CTO.
The freelancer, agency or tool that launched it can no longer keep up.
You want to set priorities without hiring or managing developers.

No, if

You are looking for a technical co-founder who takes equity: Figue is a provider, not a co-founder.
The product does not exist yet, or everything must be rebuilt: start with a fixed-price project.
You want one person full-time just for you: the team is shared, with one dedicated point of contact.

See fixed-price projects

How much does it cost, with no CTO and no hire?

One fixed price, every month.

No salary, no hiring, no equity. A monthly subscription you can stop at the end of the period.

€1,490/month ex VAT

Per slot, for the next clients, locked for 12 months. Public rate: €1,990/month ex VAT.

See the offer and tiers

One active request at a time per slot, a queue with no limit.
No commitment, cancel at the end of the period.
Production starts after an onboarding call.
Hosting, licences and third-party APIs stay on your side.

Non-technical founders: frequently asked questions

The right questions.

What to read when you have no CTO?

What we wrote on the subject.

Three custom trays connected by an orange channel.

Building

7 August 202610 min

Having your first business software built when you are not technical

You know your trade, not software. Here are the reference points a non-technical owner lacks: your real edge, the three traps, and how to de-risk before coding.

An orange pointer guides several models on a circular platform.

Tech leadership

4 August 20269 min

Fractional CTO: what it is, when to bring one in, and how to choose

A product taking off, a small team, and no one to arbitrate the technical choices that will shape the next five years. A fractional CTO fills that gap without the cost of a full-time hire. When to bring one in, what they really do, how much it costs.

Cover reading Taking over code from a vendor, on a sand background with an orange disc.

Building

22 September 20268 min

Taking over code from a vendor: the checklist before changing providers

Taking over code from a vendor means handing a new team software it did not write, to maintain and evolve it. For companies changing providers: what to recover, what the incoming team must check before promising, and why a takeover is not a rewrite.

Two halves of an arch joined by an orange keystone.

Strategy

7 August 20269 min

Vendor or partner: how to choose who builds your software

Every vendor says the same thing. What separates a partner from a mere executor is the incentive. Seven questions and a few signals to tell them apart.

START FROM YOUR PRODUCT

You decide, we build.

Show us your product as it is. We tell you what holds, what is pressing, and whether the subscription is the right answer.

See the offer and price