Skip to main content

Strictly necessary · always on

Remembers this choice in your browser. No tracking.

Start with something that works.

Every partnership starts with a First Build: about a month, a fixed price, and a working slice on your real data or your real device. Then a fixed quote for what comes next. We start two to four a year.

Illustration of the three shapes of working together: First Build, Outcome Project, and Product Partnership

The hard part is deciding what to build.

What to build, what to refuse, and what a regulator will accept. That is the work.

Most products stall because nobody owns the roadmap. We sit with the founders, ask the hard questions first, and take the result as ours.

What we believe

Three things we will not negotiate.

The rules that make partnerships last for years.

Your business is the metric.

A partnership succeeds when your business does. Not when the sprint closes. Not when the app ships.

We own the result.

Roadmap, build, run, support. One name on the outcome, and it is ours. The IP is yours. The direction is set together, in the same room.

A bug is a recall.

So we build like it. Requirements trace to tests, every release is verified, and the evidence comes out of the same pipeline that ships the product.

Who we take on

What fit looks like, on both sides.

We take on

  • A real product with a real constraint: hardware, data, regulation
  • Founders and executives who want to be challenged, not agreed with
  • Work where a bug is a recall and intelligence changes the business, not just the interface
  • Relationships meant to last years

We pass on

  • Work without a named outcome
  • A single discipline on its own, without the product around it
  • Decks without a build, and compliance treated as paperwork
  • Work without an owner on your side

What makes it work

  • An owner who can decide
  • Real data, a real device, or a real workflow
  • What you tried before, and what it cost
  • A problem worth owning

How it starts and how it continues

Three shapes, in the order they happen.

First Builds start at $100K. Everything after is quoted from what the First Build shows. Never billed by the hour. Never quoted by the head.

Tell us what you're building
An engineer leaning into a hardware rig, checking the device up close
a)Fixed price · About a month

First Build

About a month on your real data or your real device, against success criteria we agree in week one. You leave with a working slice, the architecture and the evidence plan, and a fixed quote for what comes next. Every long partnership we have started with a fixed-price build.

A surgeon at work under the operating-room lights
b)Fixed price · Three to six months

Outcome Project

One named outcome, in production, in three to six months. Billed against the plan. The IP is yours from day one.

Two clinicians leaning in together over the operating table
c)Ongoing · Six-month minimum, reviewed quarterly

Product Partnership

The whole studio behind your product for as long as it keeps growing: product, design, engineering, and AI, on one roadmap. The IP is yours. The direction is set together. Ninety days' notice, either way.

In their words

“We have worked with SpiceFactory for years. They keep coming with innovative solutions all the time. Super fast product delivery cycles.”
Ken, President of Z9 Security

How we work

From the first question to the real world.

  1. Ask the hard questions

    Before anyone writes code, we sit with the founders and ask what the business must win, who the real customer is, and what failure costs.

  2. Work on the right thing

    One roadmap, cut to what moves the business. One named outcome. One fixed price.

  3. Measure and shape

    Instrumented from the first release. We learn what customers actually do and improve every week.

  4. Scale into the real world

    Built to run at the scale the business reaches. Where a regulator is in the room, the evidence is generated as part of the build, not in a sprint before the audit.

Questions

Before the First Build.

How long does a First Build take, and what do we have at the end?

About a month, at a fixed price, on your real data or your real device, against success criteria we agree in week one. You leave with a working slice, the architecture and the evidence plan, and a fixed quote for what comes next. First Builds start at $100K. Everything after is quoted from what the First Build shows.

What happens after the First Build?

You decide. The slice, the architecture, and the plan are yours whether we continue or not. If you go on to the next stage, the First Build is credited against it. An Outcome Project is one named outcome in production in three to six months, billed against the plan. When the product is the business, a Product Partnership follows, with product, design, engineering, and AI on one roadmap. Every partnership that lasted began with a First Build.

Who owns the IP?

The IP is yours from day one. The direction is set together, in the same room.

What changes when a regulator is in the loop?

The evidence is generated as part of the build, not in a sprint before the audit. A First Build ends with the evidence plan. Requirements trace to tests, every release is verified, and the evidence comes out of the same pipeline that ships the product. Our regulated work with partners covers HIPAA, SOC 2, and PCI DSS, and the verification evidence that went into Canary Medical's own FDA De Novo submission.

Read the Canary Medical story

What do we need on our side to start?

An owner who can decide, and real data, a real device, or a real workflow to build on. It helps to bring what you tried before, and what it cost. We pass on work without a named outcome or without an owner on your side.

How long do partnerships last?

As long as the product keeps growing. A Product Partnership has a six-month minimum, is reviewed quarterly, and ends on ninety days' notice, either way. Our longest partnership began in 2015. Nobody keeps a vendor that long. They keep a partner.

How many new partnerships do you take on a year?

We start two to four new partnerships a year. The rest of the year belongs to the partners who stayed. A founder reads every message and answers within two working days, including when the answer is no.

Contact

What would you build first?

A First Build is the smallest real thing we can make together: a working slice on your data or your device, the architecture, and a fixed quote for what comes next. Tell us what you are building, what the business needs to win, and who owns it on your side. A founder reads every message and answers within two working days, including when the answer is no.