Keep It Yours

For Educators

Teach Founders What They Need to Own Before Something Goes Wrong

Keep It Yours is a practical curriculum supplement that teaches student founders to own and control the digital infrastructure their future companies will depend on — before fragile foundations become expensive mistakes.

Entrepreneurship professorsMBA professorsBusiness schoolsEntrepreneurship programsUniversity incubatorsAccelerators

Why this belongs in entrepreneurship education

Entrepreneurship students learn finance, accounting, legal structures, marketing, fundraising, and strategy.

But many graduate without understanding who should own and control the domain, cloud infrastructure, source-code repositories, administrative accounts, payment systems, and other digital assets their future companies depend on.

It's a gap between knowing how to start a company and knowing how to keep control of one. Keep It Yours is designed to close it.

Topics covered

The book works through the concrete systems every founder should own or control — the same categories students will confront in their own ventures.

Domains & DNS

Who legally owns the domain, and why registrar control matters more than the website itself.

Cloud infrastructure & hosting

Company-owned accounts versus infrastructure quietly tied to a contractor or co-founder.

Source-code repositories

Ensuring the company — not an individual developer — owns and controls the codebase.

Administrative accounts & access

Root access, recovery methods, and the accounts that quietly hold the whole company together.

Payment & billing systems

Moving billing off personal cards and into durable, company-owned financial accounts.

Analytics & business data

Owning the customer data, analytics, and records a company depends on to operate.

Email & identity

Company-controlled email and identity providers instead of personal inboxes.

Vendors & agencies

Structuring outside relationships so delegating work never means surrendering control.

What students will be able to do

  • Identify the systems a founder needs to own or control.
  • Explain why unclear ownership creates avoidable startup risk.
  • Tell the difference between delegating work and surrendering control.
  • Map the domains, accounts, vendors, tools, and access points behind a startup.
  • Create a practical infrastructure ownership checklist for a new venture.

Suggested classroom uses

  • 1Assign as supplemental reading in a new-venture creation or startup launch course.
  • 2Turn the infrastructure ownership checklist into a hands-on assignment for student ventures.
  • 3Anchor a class session on operational risk and the non-obvious responsibilities of founders.
  • 4Pair with a capstone project: have teams audit the infrastructure of a real or simulated startup.
  • 5Use as a pre-accelerator readiness exercise before students take on customers or funding.

Discussion questions

Ready-to-use prompts for seminars, breakout groups, or reflection assignments.

  • If your technical co-founder left tomorrow, what exactly would your company lose access to?
  • Who legally owns your startup's domain — the company, or a person?
  • What is the difference between delegating work and surrendering control?
  • Which accounts should never be tied to an individual's personal email address?
  • How would you recover a locked administrative account with no documentation?
  • What belongs in an ownership handover before you hire an agency or contractor?

Bring it to your program

Beyond the book, the authors work directly with programs and cohorts.

Guest lectures

A 30–45 minute session for entrepreneurship classes and student founder programs: Own What You Build — Startup Infrastructure Mistakes Founders Should Avoid Early. Covering domains, email, password management, cloud platforms, source code, billing, vendor access, and documentation.

Workshops

A hands-on working session where student teams audit their own ventures and build a real infrastructure ownership checklist they leave with. Well suited to incubators, accelerators, and venture labs.

Course adoption

Considering Keep It Yoursas required or supplemental reading? We'll work with you on the format that fits your syllabus, term, and cohort size — and answer any questions before you commit.

Bulk & student access

Need copies for a whole class or cohort? Tell us your program and rough headcount and we'll help you arrange access for your students.

About the book

Keep It Yours was written by Joe Kaire and Allan Torres from years of helping founders navigate infrastructure decisions at critical stages of growth.

“If you don't own it, you don't controlit.”

Built for founders who want to build with intention — and for the educators preparing them to.

See the full book page, contents, and format

Instructor review copies

Tell us a little about your course or program. Whether you want a review copy, to discuss adoption, or to invite an author to speak, this form reaches us directly — we'll follow up within 2 business days.

By submitting, you agree to be contacted about your review copy request. We'll follow up within 2 business days.

Prefer to reach out directly?

Email us with any questions about using Keep It Yours in your program and we'll be glad to help.

support@jokertechnologies.com