GTM OS Founding group The project →

GTM OS · Founding group

You raised your hand.
Here is what happens now.

You signed up to deploy GTM OS for your own clients. This page is the answer, written once so nobody gets a different version of it.

  1. 01
    Book a 30-minute call with me

    Your projects, your stack, what you would install first. No deck.

  2. 02
    Take a seat in the founding group

    Ten implementers who build this with us while it is still closed. One hour together, then 30 minutes a week.

  3. 03
    Run the rules book on one real company

    Yours or a client's, in September, with our engineers on the call. This part starts before the software is finished.

Book the 30-minute call Ten seats · eight taken

What you would be deploying

GTM OS is open-source software that runs a company's marketing and sales motions on its own data, by definitions the team writes down once and every tool, agent and person then follows.

Your motions, run on your data, by your rules, on code you own

Every company runs the same handful of motions. Outbound, lead scoring, SEO and GEO, paid ads, lifecycle. About eighty percent of the code behind them is identical from one company to the next. The twenty percent that differs is the wiring to their tools and their definitions.

We package the eighty once, as open code. The twenty gets written with the client. That written, signed set of definitions is the rules book. It is the part this group exists to get right.

Read the full explanation →

Where it stands, honestly

Closed alpha. No public launch date.

You are being invited in before it is finished, which is the whole point of a founding group. Here is exactly where the build is, with nothing rounded up.

Phase 0
September

Proof. One motion running end to end on one real company, from a blank sandbox to a deployed app. Two weeks of work.

In build
Phase 1
October

Motion one, closed alpha. Outbound plus signal scoring. Five objects, five building blocks, five connectors. The founding group installs it into their own stacks.

Next
Phase 2
No date

The AI engineer. You say "change our ICP from SMB SaaS to enterprise logistics" and the system works out every object, agent and app that has to change.

Planned

The repo opens on a condition. It opens after this group has shipped it on live client work, when it is good enough that you would not look at it and say you could have built it yourself. We are not putting a date on that on purpose.

I told some of you three to four weeks for motion one. Update. The founding group sees it run end to end in that window, on one real company. Installing into your own stack is October. The public repo comes after that. We chose to do the definitions work first because that is the part that breaks every project.

The founding group this month

Three things, none of them waiting on finished software

Everything below is work we can do in September while Phase 0 is still being built.

01 · THIS WEEK

The 30-minute call

Me and you. What you are working on, what you would install first, whether this is worth your time. You leave knowing if you want a seat.

02 · SEPTEMBER

One 60-minute working session

Thirty minutes with me on your projects, stacks and goals. Thirty minutes with Walid and Marwan, our architect and our engineer, on where your builds actually break.

03 · SEPT TO OCT

Thirty minutes on Wednesdays

A standing call with the people building it. You see what shipped, you say what is wrong, it changes the following week.

The deal

What you give, what you get

Written out fully so there is nothing to discover later.

You give

  • One 60-minute working session with me, Walid and Marwan.
  • Thirty minutes on Wednesdays through September and October.
  • One real company to run the rules book on, yours or a client's. From that company, read-only access to its top two or three tools, one two-hour definitions session, fifteen minutes a week of feedback for a month.
  • Straight feedback in writing when something is bad.
  • Nothing else. No fee, no exclusivity, nothing to sign this month.

You get

  • A founding-group seat, listed by name when the repo opens.
  • The method now, walked through with me. The rules-book template, the canonical tables, the four motions we have built most often.
  • A first install on the company you bring, free, with the core team's engineer hours. Installs start in October, one company at a time, in the order the seats were taken.
  • Certification in the first cohort, free.
  • Your own rates on every install you do after that.
  • A referral fee, agreed in writing, on engineers placed through you.
  • Mutual case-study rights.
  • The founding channel, a direct line to the people building it.

The money

How a certified expert gets paid

Three things are settled enough to put in writing. Everything else we work out on the call.

  1. You install at your own rates and you keep the fee. The code is free. The install is craft. Craft is paid work.
  2. When a client of yours needs an engineer, we place one from our bench and you are paid a referral fee, set in writing with you before the first placement.
  3. The first cohort trains free. Your name goes in the certified directory when the repo opens. We can both use the work as a case study.

Anything beyond those three, territory included, we agree on the call and put in writing before anything is owed. I would rather tell you the number once it is real than quote you one I have not settled with my partners.

What certified means

One standard, one sentence

The software will keep changing under you for a year. The method holds, so the method is what we certify.

A certified expert has shipped one install with the core team and can run the rules-book step on a client alone.

The training is non-technical. It is the same conversation you already have with clients, with the parts that break named in advance.

How it worksThe architectureThe wordsThe stepsThe roadblocks

Next step

Thirty minutes and you will know whether you want a seat

Eight of the ten seats are taken. If the timing is wrong, tell me and I will keep you posted instead.

Book the 30-minute call

Would rather write than book? Email me at david@humanoidz.ai and I will answer myself.

GTM OS · founding group

internal · not for sharing