OPERATIONOWNERSHIPEST. 2026 · COHORT 01Cohort 01 · 8 seatsApply
Apply for Cohort 1
OPERATIONOWNERSHIPEST. 2026 · COHORT 01OPERATION OWNERSHIP · COHORT 01 · 8 SEATS

Stop Renting Your Dev Team. Own the Build in Eight Weeks.

If a team overseas builds and fixes your app, you are renting it. In eight weeks you take it back. You run the AI the way you run people, you approve the work, you launch the same day. If they built it, we bring it home. I do not write code. Neither will you.

Apply for Cohort 1

8 seats · $5,000 · I read every application myself

STANDING ORDERBy the end of eight weeks your app is live, it works, and you have the AI team that keeps it working, or I keep working with you until you do.

In plain English: you leave with a live app and the AI team that keeps fixing it. Or I keep going with you.

No. 01 / Sitrep / What you've been told

The Noise.

  • No. 01
    "Just hire a team in the Philippines. My guy pays them nothing."
  • No. 02
    "Put it on Upwork. You will get it done for a third."
  • No. 03
    "The senior dev is out until Monday their time."
  • No. 04
    "It is complicated. You would not understand the code."
  • No. 05
    "That is out of scope. I will send a change order."
  • No. 06
    "It works on our side."

It isn't you. Nobody is teaching owners how to be in charge of the build.

You did what everyone told you to do. The rate looked good. Then the invoices kept coming, the fixes waited for their morning, and one person understood your payment code and you could not afford to lose him. You do not know what is inside your own app. So you looked at AI. Someone said it could build anything. You tried, and it built something impressive for ten minutes, then it broke and you had no idea why. Or you never tried, because where do you even start. Here is what nobody says. You do not need to learn to code. I never did. You need to know how to run a team, and you already know that. You tell them what you want, you check what they hand you, you send back what is wrong. That is the whole skill. I show you how to do it with AI instead of a team you rent.

You can keep paying the retainer and waiting for their morning. You can spend a year reading about AI. Or you can own the thing.

No. 02 / After action report / 2009 to 2013

I was the guy who outsourced.

ONE WAYCOFFEECORDON BLEULAS VEGAS · 2013CEBU · TYPHOON YOLANDA10 DAYS · 9 PEOPLE · 1 ROOMTHE FUNDERS

THE FLIGHT + THE STORM + 10 DAYS + 9 PEOPLE =NOTHING.

I got out of the Army in 2009. I spent a year as a government contractor making six figures at twenty-five, and I saw the ceiling anyway. No matter what they paid me, someone else owned my time. I read The 4-Hour Workweek and that was all I needed. Leverage and freedom, and the way there was overseas. I hired dozens of people in the Philippines. I built teams for other owners. I was better at outsourcing than anyone I knew. Then came Cebu.

  • The flightIn November 2013 I had an app that people with money were waiting on, a team of developers in Cebu, and a deadline that would not move. So I got on a plane in Las Vegas. I landed in a typhoon. Typhoon Yolanda. It swallowed whole islands, and my plane got in right before it hit. I woke up to palm trees thrown across the property like twigs.
  • The hotel roomThe plan was an Airbnb. The first was a loft with the whole team in it, and we had it one day. The second was across town, and the men who followed us there were not interested in the app. My team told me not to stay. I listened. We finished out of the Mandarin hotel. Nine developers and designers. One hotel room. Ten days. Coffee, and chicken cordon bleu off the hotel menu.
  • Day 10 · LaunchOn day ten it launched.
  • The fundersThen the money people said no.

The flight, the storm, ten days, nine people.

All of that work for nothing.

Overseas teams gave me leverage. They never gave me ownership. Fly there, sit in the room until it launches, and it is still theirs. Here is what took me fifteen years to see. I never wrote a line of code in Cebu. I never have. I ran the company that built hundreds of pieces of software for other people, from an app for an ice cream store to an education system as big as Blackboard, and my job the whole time was the same: know what needs to exist, know how the pieces fit together, tell the builders exactly what to build, and check what came back. That was always the job. The mission has not changed since 2009. The team has.

No. 03 / Sitrep / Current position

Renting. Owning.

Renting

A flight through a storm. A hotel room for ten days. And after launch it did not stop. A monthly bill to keep the team around. A list of bugs that sat there until the team woke up on the other side of the world. One guy who understood how the payments worked. He quit, and he took the understanding with him.

Owning

Five or six AI workers on my kitchen table. One builds. One checks the first one's work. One tests. One hunts yesterday's bug. They run my servers, my databases, my app, my email. I have never written code and I still do not. I tell them what I need the way I told a team of nine in a hotel room in Cebu, and I read what comes back. Nobody flies anywhere. Nobody quits. Nobody owns my software but me.

WHAT MY AI DID FOR ME TODAY · STARTED THE APP · SET UP THE DATABASE · THE SITE WENT LIVE · RAN TWENTY CHECKS · FOUND AND FIXED A BROKEN EMAIL SENDER · I TYPED NONE OF IT

Morning Coffee

Here is the part nobody sells you. Building the app is the first cost. Keeping it alive used to be the second, forever, and it was paid to someone else. Now the same AI that built the app looks after it overnight. It finds what is slow, what broke, what needs updating, and it writes up the fix. In the morning I read what it did with my coffee. I say yes to some. I say no to some. Nothing goes live unless I say so.

The AI proposes. You approve. That is what owning it looks like.

No. 04 / Briefed on the call

The Reveal, Withheld.

Three decisions decide whether AI becomes a team you own or another thing you rent and cannot see inside. Get them right and it works like a team that never sleeps. Get them wrong and you are waiting on somebody again. Here is the first one for free. The other two I show you on the call, on your app, before you have paid me anything.

DECISION ONE · FREE

Which AI does which job. One builds, one checks, one tests. The reason it broke on you last time is that one AI was doing all three and nobody was checking its work. You do not need to understand how any of them work. You need to know who is on the job. That is a manager's question, and you already answer it every day.

THE THREE DECISIONS01 Which AI does which job. 02 How they check each other's work. 03 What you do when something breaks. I'll show you on the call.
MORNING COFFEEYour app gets better while you sleep. You say yes or no over your morning coffee. I'll show you on the call.
Apply for Cohort 1

On the call I set this up for your app. You keep that whether or not you join.

No. 05 / Mission objectives

What You Walk Away With.

Week one you ship one real change to your own app. Not a demo. Something your customers see. Here is where you are at the end.

  • 01

    Your app, live.

    The thing you have been trying to launch is launched, working for your customers, and a change you ask for goes live the same day. No ticket, no quote, no waiting for someone's morning.

  • 02

    No bill to keep it alive.

    The retainer ends. The AI team that built the change keeps the app working, on your own computer, with written job descriptions you understand: one plans, one builds, one checks the builder's work, one tests so nothing else breaks, one watches overnight. It does not quit and it does not invoice.

  • 03

    A room you keep.

    The Ownership Room. The owners from your cohort, the ones after it, and me. When something breaks at 2 a.m. in month four, that is where you ask, and someone answers.

After this, your daily job is reading three proposals and saying yes or no. It takes a coffee.

By the end of eight weeks your app is live, it works, and you have the AI team that keeps it working, or I keep working with you until you do.

No. 06 / Week by week / What you have at the end of each

Eight weeks. What you have.

  • Week 1

    Your app read back to you in plain English: what it is made of, who holds the keys, what breaks first. Every login and password in your hands. And one real change your customers can see, live, made by your AI team with your yes.

  • Week 2

    Your team, hired once. Five AI workers on your own computer with written job descriptions: one plans, one builds, one checks the builder's work, one tests so nothing else breaks, one watches overnight. You watch the checker send work back for the first time. Nobody to interview, nobody to onboard, nobody who leaves with the training.

  • Week 3

    The backlog moving. The bugs and small fixes that sat for months go to the team; you read what comes back each morning and say yes or no. By Friday the list is shorter than it has been in a year.

  • Week 4

    Your first feature. Something you wanted and never got: described in your words, planned, built, checked, tested, live. You did not write a line.

  • Week 5

    An app that fixes itself overnight. The overnight worker finds what is slow or broken and writes up the fix; you approve it over coffee. The morning routine is yours now. And the team remembers how you like things done: every correction you made in weeks one to four is still in force.

  • Week 6

    The scary parts, understood. Payments, sign-ups, the pieces nobody let you touch: explained in plain English, and changed safely by your team with the checks that prove nothing else broke.

  • Week 7

    A week run without me. You plan, approve, and go live on your own for five days. I watch and correct. This is the test.

  • Week 8

    The keys, the book, and the room. Everything about your app written down in plain English for the next person or the next AI. Your accounts and your code in your name. The Ownership Room for month four at 2 a.m. And the bill for keeping it alive is gone.

No. 07 / Selection criteria

Select. Do Not Select.

This is for you if

  • You pay a team overseas to build or maintain your software, or you are about to.
  • You run a business. You know what it is to own a result.
  • You have tried AI and it did not stick, or you have not started because you do not know where to.
  • You can give this six to ten hours a week for eight weeks.

This is not for you if

  • You want someone to build it for you. That is what you have now, it is why you are here, and I do not do it at any price.
  • You want the cheap version. Eight owners, eight weeks, my calendar. There is no cheaper version of that.
  • You will not open the laptop. If six hours a week is a stretch, keep the retainer. That is the correct decision and I will say so on the call.
  • You want to argue with me about which tool. I pick the tools. If that is a problem, we will both know in ten minutes.
No. 08 / Commanding

T.J. Typinski II

10th Special Forces Group · White House Communications Agency · Owner · Not a programmer

T.J. Typinski II

I am not a technical person. I have never written a line of code and I do not intend to start. I got out of the Army in 2009, hit the ceiling as a contractor inside a year, and decided to own myself. I built a development company and ran it for fifteen years as the project manager, not the engineer. We built hundreds of pieces of software for other people, from an app for an ice cream store to an education system as big as Blackboard. My job was knowing how systems fit together, managing the people who built them, and saying exactly what a builder needed to hear without pretending to understand the code. I did that with dozens of hires in the Philippines. I do it now with AI, which also runs my servers. Before all of that: Army at eighteen, 10th Special Forces Group, Iraq at nineteen, four years with the White House Communications Agency.

  • 2001 to 2004US Army Special Forces. 10th Special Forces Group at eighteen. Iraq by nineteen.
  • 2004 to 2008White House Communications Agency. Presidential travel, worldwide.
  • 2009Out of the Army. A year as a government contractor, six figures at twenty-five, and a ceiling. Read The 4-Hour Workweek. Decided to own myself.
  • 2009 to 2024Dominant Approach. My development company. I ran it as the project manager, never the coder. Hundreds of pieces of software for other people, from an ice cream store app to a Blackboard-scale education system. Dozens of hires in the Philippines. The 2013 Cebu build during Typhoon Yolanda.
  • 2009 to PresentFixing how other owners' businesses run. Now Lionmaker Systems.
  • 2018 to 2020Bunker Labs, Detroit Chapter. Co-founder. City Leader of the Year, first year.
  • 2019 to 2021The Lions Den. Led men through the Iron Sharpens Iron Academy.
  • 2023 to PresentReal estate, Detroit. The newest of more than a dozen businesses. 10+ properties a year.

Units I've led

  • Bunker Labs Detroit. Co-founded the chapter. Veterans starting and growing businesses. City Leader of the Year in year one.

  • The Lions Den. Led men through the Iron Sharpens Iron Academy.

  • The Ownership Room. This one. Owners, held to owning their software.

No. 09 / Record

Cohort 1 is the first. Proof will be posted as it launches.

  • Units ledBunker Labs Detroit. The Lions Den. The Ownership Room.
  • What members sayNothing yet. Cohort 1 has not finished. I will not quote people who have not done the work.
No. 10 / Questions from the briefing

FAQ

I already have a team overseas. Do I fire them?

Not on day one. First you learn to own the build. Most owners keep the team for a while and stop needing them. That is your call, made from strength instead of dependence.

Do I need to know how to code?

No. I do not know how to code. I have never written a line of it, and I built a software company. You need to be able to say what you want, look at what you got, and decide if it is right. That is being the owner, not the programmer.

Which tools will I need?

The ones I pick for you. Today that is mostly Claude Code, and I will name the rest on the call. You stop shopping and start owning.

How is this different from a YouTube course?

A video is a programmer showing you a tool. I am not a programmer. I am the guy who managed the programmers for fifteen years, and I set up the whole system on your app, then I am in the room with you every week while you run it.

What does this cost me every month after week eight?

Your AI tools. No retainer to me or anyone else. I will show you your figure on the call.

How much time per week?

Six to ten hours a week for eight weeks, then a coffee a day. You are trading a permanent wait for a temporary one.

Will you build it for me?

No. That is what you have now, and it is why you are here. I build it with you, so it is yours.

What if it is not worth it?

Then I pay you back. Here is the condition. Be on all eight live sessions, do the work on your own app every week, and if you get to the end and it was not worth it, email me within seven days of the last session and I refund every dollar. If you leave early there is no refund. This is a decision, not a trial. Before you decide, send me your app and I will tell you for free what is wrong with it.

If you cannot code, what do you actually do all day?

I decide what needs to exist. I split the work up. I tell each AI worker what to build and what good looks like. I read what comes back and I approve it or send it back. Today that meant a new app, a database, a live site, twenty passing checks and a fixed email sender, and I typed none of it. That is the job, and it is the job you already do with people.

It breaks at 2 a.m. in month six and I am holding it. Then what?

The AI finds it, writes the fix, and it is waiting for your yes in the morning. If you are stuck, the room is there and so am I.

What if I don't have an app yet?

Then you are about to make the outsourcing decision, and this is the last stop before you do. If you have the idea and the time, apply.

No. 11 / Orders / Cohort 01

Cohort 1 starts Monday, November 16, 2026. Eight seats. $5,000.

Eight is the most owners I can hold to a standard at once. Ten minutes to apply. If you are a fit we talk for half an hour about your app, and you leave that call with the plan whether or not you join. You will not need to understand a word of code to follow it. I don't either.

Apply for Cohort 1

Read the terms before you apply.

Reviewed personally by T.J. Typinski II. 10th Special Forces Group. White House Communications Agency.