We build fintech & insurance products that keep growing.

Two partners, one day, at your whiteboard. We look at where it hurts, where the potential sits and what you expect from us. By the evening there is a clear focus and a concrete idea of what a first Project could look like. Within a week you get a showcase prototype and a proposal with scope and price.

Whether we are a fit at all is settled before this. That is what the fit call is for, not this day.

A Project buys an outcome: a fixed goal, a fixed date, a fixed price. If it takes longer, that is ours to carry.

Embedded buys capacity: senior partners on your team for as long as the work needs them. Most teams do a Project first and move to Embedded when it is time to go to production. Embedded starts at one day a week.

It depends on the goal and on who the work needs. Before we start, we agree the scope and a fixed price for a Project, or the days per week for Embedded, usually after the workshop.

One partner leads from start to finish, usually one you already met in the workshop: a Product Builder when the answer is an interactive prototype in code, an AI Builder when it is a technical proof of concept, both when it needs both.

Design and build come together as a rule. If you only want the design part, say so and we scope it that way.

Whoever of the three is not on your engagement comes in as sparring: key reviews, input in Slack, a second opinion when the direction changes. Up to two hours per partner every four weeks, included.

Remote is the normal case. In a Project: Slack or Teams daily, an update three times a week, a review every week. In Embedded, the rhythm follows the days you book.

You always know what we are working on and where it is stuck. We tell you before you have to ask.

We agree the working mode with you at the start, including fixed on-site sessions planned in advance. When something needs a room in between, we come to you.

If the agreed work takes longer, that is ours to carry. If the work itself grows, we tell you in the same week we see it. A Project has a fixed price and a fixed date, so the scope does not simply grow with it.

You then have three options: cut something else and keep the date, book the new work as a further Project, or add Embedded time.

What we don't do is quietly stretch the scope and send a larger invoice at the end.

Everything we made is yours: code, design files, documentation and the plan to go live.

In our experience Embedded is the fastest way to grow your team with senior people and keep full flexibility. At Nomad a proof of concept turned into five product areas. Once you have proven the need, you can still switch to hiring internally.

No recruiting, no onboarding cycle. Billed monthly, one month minimum, then two weeks' notice to stop, prorated: no overhead, no equity, no severance, no open-ended contract.

Ideal for teams that need senior capacity now, but aren't sure they need it permanently, or who have a funding round ahead and no headcount for it.

That is how a lot of our work arrives. You can contract us directly and stay your client's single point of contact, or we contract with the end client and you stay in the room.

Where an engagement needs it, we work under your name. Prices are the same either way.