Skip to content
injuid

Track B / Incubate

A technical partner, not a vendor. Three a year.

For founders with a customer problem they can describe in one sentence, someone who has already said they will pay, and no technical arm. injuid builds and runs the technical side as a partner. Reduced cash cost, equity that vests over time, and a hard limit on how many we take on.

Slots
3 per year
Cash
Reduced, not zero
Equity
Yes, vesting with a cliff
Paperwork
Shareholders agreement first

01, What it is

What this is, and what it is not.

It is

  • A partner who builds the product, runs the infrastructure, and stays
  • Someone whose upside depends on the business working, not on the invoice clearing
  • The same standard of build as Track A: proper auth, tenancy, backups, monitoring, ownership
  • A founder who can spend their time on customers instead of managing developers

It is not

  • Free development in exchange for a promise
  • A dev shop with a discount code
  • A way to get a prototype built so you can raise money and hire your own team
  • Available to more than three businesses a year, regardless of how good the fourth one is

02, Criteria

The selection criteria.

Published so you can rule yourself in or out before you write anything. Every application is read against these, in this order. Most do not get past the second one, and that is the point.

  1. C1

    You can describe the customer problem in one sentence

    Who has the problem, what it costs them, and what they do about it today. If it takes a paragraph, it is not sharp enough yet.

  2. C2

    Someone has already said they would pay for it

    Ideally in writing. A signed letter of intent, a deposit, a pilot agreement. A conversation where a real customer said yes counts. Your own conviction does not.

  3. C3

    You are on this full time, or have a dated plan to be

    A date, not an intention. Building a company on nights and weekends is possible. Building one with a partner who is also on nights and weekends is two people waiting for each other.

  4. C4

    You bring what injuid does not

    Domain knowledge, the customers, the sales, the industry relationships. If the idea is 'a software business' and the plan is that injuid builds it and then it sells itself, that is a Track A build, not a partnership.

  5. C5

    It is a software business

    Not a services business with a software feature bolted on. The product is the thing customers pay for and it works while you sleep. If it needs you in the room for every sale, it is a different kind of company and equity in the software is the wrong instrument.

03, The deal

The shape of the deal.

Specifics are agreed per company and depend on stage, cash, and what each side brings. The structure does not change.

Cash
There is always a cash component, at a significant discount to the Track A price. It is not pure spec work, because that fails everyone. A founder with nothing at stake does not push, and a builder with nothing coming in does not stay.
Equity
injuid takes a minority stake. Not fifty percent by default, and not a token amount. Enough that the outcome matters to us.
Vesting
Equity vests over time with a cliff. If the partnership ends early, the founder is not carrying dead equity, and injuid is not walking away with a slice of something it did not build.
Agreement first
A shareholders agreement, drafted by a lawyer, signed before a single line of code. It covers what happens if either side walks, who owns the code and the infrastructure, and how decisions get made.
Ownership
Domain, hosting, source, and every account belong to the company, not to either founder personally. Same rule as Track A.
Concurrency
A hard cap of 3 new partnerships a year. Dead equity is how every incubator dies. Fewer, done properly, is the only version of this that works.

04, Apply

How to apply.

The form is longer than the contact form on purpose. Every question maps to a criterion above. Short, specific answers beat long, impressive ones.

Who has it, what it costs them, what they do today
Names optional, specifics not
C3 Your time
Domain knowledge, customers, distribution
How does it make money while you sleep
Where it is today
Site, deck, prototype, LinkedIn. Anything useful.

Read against the five criteria, in order. A reply within five business days.

What happens next

Reply
Within five business days. Every application gets one.
If no
It will say which criterion and why. That is useful information.
If maybe
A call. Then a second, with numbers. Then a decision within a month.