Skip to main content
DDEFTSPAN

Selective program

Venture partnerships, subject to agreed scope and terms.

Fee-based work and selective equity arrangements are considered separately. Acceptance, staffing and operating support are not guaranteed.

Discuss partnership fitSee scoped engagements instead

What we bring

Architecture, engineering and operating responsibilities can be discussed as a proposed scope. Delivery and staffing require confirmation.

What we ask

Any equity, cash expenses, vesting, governance, IP, operating duties and exit terms require a separately agreed contract.

What we don't ask

No default cash, control, veto or ownership policy is established here. Resolve these terms before either party commits.

Availability and the commercial arrangement require mutual agreement; this page does not reserve capacity or approve an application.

Selection

Factors to discuss.

  • A founder with real domain depth — you know the workflow better than any consultant could learn it.
  • A problem where software is the bottleneck, not distribution or capital.
  • A first release with bounded scope, dependencies and acceptance checks agreed before work.
  • A commitment to sell: we build and operate, you own the market.
  • Comfort with an equity arrangement documented properly, with vesting and a defined scope of work.

Constraints to assess.

  • Ideas that need validation before they need engineering.
  • Projects unwilling to agree delivery, ownership and operating responsibilities.
  • Work where the founder intends to disengage after handover.
  • Anything requiring a regulated licence neither party holds.

Apply

Make the case in a few paragraphs.

What the workflow is, why you understand it better than the incumbents, what the first release must do, and what you are bringing that we cannot. Submitting does not confirm acceptance or a response deadline.

Partnership application

Name, email and a brief description are required. The other details are optional. Please do not include credentials, sensitive customer records or regulated documents.

Scope and availability require agreement. A non-binding enquiry only; future proposals are in USD after understanding your needs.

We use submitted details to assess and respond to your request. Hosting and communication providers may process them on our behalf. Do not send sensitive material; any secure channel and access must be agreed separately.

Who we serve here · Proposed hypothesis

Who is involved, and what each person receives at the end.

A founder with deep industry knowledge and a validated problem, but no engineering team.

Process owner

Named workflow decision owner

Needs: Define scope, permitted work and acceptance.

Doubt: Responsibility becoming unclear between people.

Proposed deliverables · agreed in scope

  • • Proposed acceptance, approval and handover responsibilities as agreed

User

Founder

Needs: A technical partner who builds and runs the platform.

Doubt: Giving equity to someone who leaves.

Proposed deliverables · agreed in scope

  • • A first release with scope and schedule agreed
  • • Any equity, fee or vesting terms agreed separately

Buyer

Co-investors

Needs: Confidence the build is real and owned.

Doubt: Outsourced code with no owner.

Proposed deliverables · agreed in scope

  • • Architecture documentation and repository terms agreed before setup

Responsibilities, not a promised roster: economic buyer, process owner, user, technical approver and operator may overlap. Explore the Finance illustrative example →·MSP illustrative example →.

Our promise

If there is mutual fit, we agree equity or fee terms, delivery scope and operating responsibilities before work

Holds when

  • • Criteria on the partnership page are met
  • • Terms are signed before work starts

Limits — what we don't promise

  • • Acceptance and capacity are not guaranteed
  • • No guarantee of funding or revenue

Evidence, labelled honestly

Context = portfolio direction, not operational acceptance · Proposed = our method, not yet proven for this audience · Unknown = we won't claim it yet.

Access we ask for — and how you take it back

  • • Shared company accounts owned by the venture

Account and repository ownership, access and exit terms are agreed before setup.

Initial inquiry: non-sensitive summary only. Later assessment: authorised redacted samples or read-only access. Sandbox and production write access require separate approval, minimisation, access expiry and retention agreement.

Exit terms define handover of code, accounts and docs.

Something useful to pass along

A build-status summary for co-investors.

Useful to: Angels and early investors.. Shared only if you choose to.

Why you'd come back: Ongoing operation and roadmap as a partner.

What we watch for harm: Founder dependence on us for routine changes.