Startup Education

Who this lecture is for

Built for accelerator and incubator programme managers assembling a founder cohort, municipal young adult centres and business departments running entrepreneurship evenings, university and college entrepreneurship centres, and small and medium business owners' forums where members keep asking whether their business could be a startup. It also suits welfare and human resources coordinators who want an enrichment session with a real decision inside it. Mixed rooms are welcome, because the comparison gives both the product founder and the bakery owner something to act on.

Questions about this lecture

I already run a profitable small business. Can it become a startup, or would I need to start something new?

Both routes exist and the lecture treats it as a decision rather than an upgrade. We look at what would have to change in the model itself, not just in ambition, and at which existing businesses genuinely carry a scalable core versus which are healthy exactly as they are. Owners usually leave with a clearer answer than the one they came in with.

Is a services or consulting business ever a startup, or does it require a product?

This comes up in almost every room. The lecture works through what makes revenue repeatable without adding people in proportion, which is the real test, and shows where a services business can carry a product inside it. Participants who conclude their business is not a startup are not being told they failed, they are being told to stop applying rules written for a different game.

If a venture turns out not to be a startup, what funding routes stay open to it?

The comparison covers this directly, because the mismatch between funding type and business type is where a lot of owners get stuck. We separate capital that expects an exit from capital that expects repayment, and look at what each one asks of the owner in exchange. Nobody leaves thinking venture money is the only serious money.

How does the lecture handle the failure rate that entrepreneurship content always leads with?

It refuses to use it as a scare statistic. Raising anxiety without giving anyone a decision framework is the standard move in this space and it helps nobody. Instead the session treats risk as something you size and bound before you commit, so the room ends with a way to test an idea cheaply rather than with a vague sense of dread.

How much ownership does the startup path usually cost a founder?

Rather than quoting figures that shift with the market, the lecture explains the mechanism, why outside investors need a meaningful share, how each round changes the founder's position, and what that means in daily practice for who decides what. Participants get the logic, so they can read any specific offer they later receive instead of memorising a benchmark.

Who this lecture is for

Written for accelerator and incubator programme managers who need a numbers session inside a founder cohort, and for startup chief executives booking an internal session for people who never studied finance, meaning product, marketing, community and operations staff. Growth and marketing leads whose teams optimise channels without a payback rule get direct value, as do angel and investor clubs preparing members and portfolio founders to speak one metric language. Outsourced finance directors and advisory firms book it when a client's model reports revenue but never cost per customer.

Questions about this lecture

Does this work for a business that is not subscription based, such as a marketplace, hardware or a services company?

Yes, and that gap is deliberate. Almost everything published on this subject assumes a subscription product, which leaves marketplaces, hardware, services and long-cycle business-to-business companies guessing. The lecture works from the underlying question, what one customer costs and what one customer returns, then shows how that question changes shape in each of those models.

Which costs belong inside customer acquisition cost, and does founder salary count?

This is the honest numbers problem and the lecture spends real time on it. Models get flattering when overhead, founder time and the cost of serving a customer quietly move to whichever line looks better. The session sets out a consistent way to draw those boundaries, and shows what happens to the picture when a team draws them differently.

What do you do when the company is too early to have real retention data?

Most rooms are in exactly that state. The lecture covers what an early company can measure honestly, how to build an estimate that is labelled as an estimate rather than dressed up as a fact, and which early signals genuinely tell you something. It also names the point at which you have enough data to stop guessing.

Will product and marketing people follow it without a finance background?

That is who it is written for. The terms arrive as acronyms, LTV, CAC, churn, ARPU, and half a room usually guesses at them in silence. The session gives everyone the same plain definitions first, so a board update or an investor conversation stops sounding like noise to the people who are actually driving the numbers.

How does this connect to what investors and lenders here actually ask?

Directly. Weak metric literacy has a financing cost, because the people deciding whether to back a company increasingly examine efficiency per customer rather than headline growth. The lecture frames each metric the way it gets asked about in a real meeting, so founders recognise the question when it arrives rather than translating it on the spot.

Who this lecture is for

Aimed at accelerator and incubator programme managers preparing a cohort for demo day and first investor meetings, founder communities and angel clubs running pre-round preparation, and university and college entrepreneurship centres that need a fundraising module inside an existing course. Corporate innovation and venture arms book it to brief internal teams on how the startups they evaluate get financed. Outsourced finance directors and advisory firms with startup clients use it as the neutral teaching session their own published explainers were never designed to be.

Questions about this lecture

Does the session cover pre-seed and Series A, or only the seed round?

It covers the progression, which is the part most published guidance skips. Almost everything available locally stops at seed, so founders learn one round in isolation and then meet the next one unprepared. The lecture treats each stage as a set of expectations the previous stage was supposed to produce evidence for.

Do you address grants and other non-dilutive funding alongside equity?

Yes, and it is one of the clearest gaps in what founders are usually told. Guides written by people who sell equity-related services tend to present equity as the only route. The session puts dilutive and non-dilutive capital side by side and asks what each one costs the founder, in ownership, in reporting and in the freedom to change direction.

Will founders learn what is actually inside a term sheet?

Yes. Term sheets get named in most content and opened in almost none. The lecture goes through the clauses that decide what a founder is left holding, valuation, the option pool and where it comes from, liquidation preference, pro rata rights, and board composition, in plain language rather than legal phrasing.

What traction evidence does each stage expect, and how do founders know they are raising too early?

This is the spine of the session. Each stage is framed by the proof it expects rather than by a target amount, so founders can look at their own evidence and place themselves honestly. Raising too early burns the introductions you cannot get back, so the lecture is equally clear about when to wait.

Is this relevant to founders outside technology, or is it venture capital specific?

Both audiences get value, but they get different things. Venture logic is explained properly, including why a fund's own economics make it reject good businesses that simply do not fit its model. Founders outside technology leave understanding why that door is closed to them and which financing doors are open instead, which is a more useful outcome than a rejection they never understood.

Who this lecture is for

Built for startup founders and small product teams with no Scrum Master, no Product Owner and no project management office, the audience the local Agile training market skips almost entirely. It also serves research and development leads who want the principles back without another certification track, human resources, learning and organisational development managers programming a team day, and non-technical functions such as sales, service, finance and marketing that were told to work in an agile way and never had it translated into their own work.

Questions about this lecture

Does this cover Lean startup and MVP thinking, or only Scrum, Kanban and ceremonies?

Lean gets equal weight, which is unusual here. Most local training treats Lean either as manufacturing-style process improvement or as a footnote inside a strategy day for executives. The session gives build, measure and learn, minimum viable products and validated learning their own space, because deciding what to build matters more than the cadence you build it in.

Does it work for a small startup team with no Scrum Master and no Product Owner?

That is the intended room. Nearly all available training assumes an organisation that already has those roles, plus a backlog structure and a project office to support them, which leaves a five-person team nothing usable. Everything here is scaled to a team where one person often wears three hats.

Do you cover when Agile is the wrong choice and when to drop a ceremony?

Yes, and it is one of the reasons the session exists. Every vendor sells its own framework as the answer, so nobody teaches the limits. Teams leave able to say out loud that a particular ritual has stopped producing anything, and to retire it deliberately instead of attending it resentfully.

Is there anything for managers, given that most Agile adoptions stall at the management layer?

There is, because teams changing while their managers do not is the standard failure pattern. The lecture covers what managers have to give up, mainly the habit of being the decision point for everything, and what changes in how progress gets reported upward. Without that part, teams do the new rituals and the old dynamics stay exactly where they were.

How does this differ from the Scrum Master and Product Owner courses our people already took?

Those courses teach a framework and issue a credential. This one goes at the principles underneath, and specifically at the gap between running the practices correctly and getting a better outcome. It is the conversation for teams who did the certification, followed the process, and still cannot point to what improved.

Who this lecture is for

For university entrepreneurship clubs and business school venture programmes running founder evenings, accelerator and pre-accelerator programme managers who need a structured validation session inside a cohort curriculum, and innovation and community managers at coworking hubs and municipal business houses booking founder track content. Consulting firms hosting founder meetups book it as the outside voice in the room. Corporate innovation leads and product groups inside established companies use it before committing development budget to a second product line.

Questions about this lecture

Which metrics do you teach for measuring fit, and do they differ for business-to-business and consumer companies?

They differ substantially, and the lecture keeps them apart. A consumer product and an enterprise product produce completely different signals, on completely different timescales, and applying one set to the other is how teams convince themselves too early. Participants leave knowing which handful of measures their own model should be watching.

We already have paying customers. Does this still apply, or is it only for pre-revenue teams?

It applies most sharply to companies with revenue, because early revenue is the easiest thing to mistake for fit. A few enterprise pilots from warm contacts can look identical to a market, right up until spending scales against that signal. The session gives paying companies a way to test whether the demand is real or borrowed.

How do you handle the local reality where early customers arrive through personal connections and give biased feedback?

Head on, because it is the specific trap here. A well-connected ecosystem makes customer conversations easy to arrange and much harder to trust, since people who like you answer generously. The lecture covers how to structure those conversations so the polite answer becomes visibly different from the real one, and which signals to weight instead of stated enthusiasm.

Do you cover fit for a new product line inside an established company rather than a new startup?

Yes, and it is barely addressed anywhere else. A second product inside a company with existing customers, an existing brand and existing distribution has advantages that mask weak signals, and internal politics that punish honest negative findings. The session covers how to validate under those conditions without the first product's success doing the arguing.

How do you talk about pivoting without demoralising the founders in the room?

By treating it as an evidence-based decision rather than an admission of failure. The session gives criteria for narrowing a segment, for persevering, and for changing direction, which turns a loaded emotional question into a normal management one. Founders who arrive suspecting the answer usually leave relieved that there is a method for it.

Who this lecture is for

Written for accelerator and incubator programme managers who currently outsource this slot to a law firm, university entrepreneurship clubs where co-founder teams are forming in the room, and founder communities and meetup organisers who watch co-founder conflict repeat itself. Startup people leads and finance leads preparing a first employee option plan book the version aimed at employees rather than founders. Municipal and regional business houses running founder cohorts get the case that comes up constantly, two or three partners starting a venture together.

Questions about this lecture

Do you give an actual method for deciding the percentages, or only explain what the agreement should contain?

A method, and that is the whole point of the session. Every available explainer describes the contents of a founders agreement, which is the part a lawyer will handle anyway. What founders are genuinely stuck on is the conversation that produces the numbers, so the lecture works through the inputs: past contribution, future commitment, capital, risk carried, and how to weigh them together.

Do you cover vesting, cliff and reverse vesting, and what happens when a co-founder leaves in the first year?

Yes, and they are treated as the centre of the topic rather than a technical appendix. These mechanisms decide who keeps what when someone leaves, which is precisely the scenario founders never plan for. The session also covers reverse vesting on shares already issued, which is the awkward case teams discover only when they need it.

Can this be run for a team that already split the equity and now needs to change it?

Yes, and a large share of real demand looks exactly like that. Renegotiating an existing split is harder than setting one, because somebody has to give something up in front of the others. The lecture covers how to open that conversation, what makes it survivable, and which mechanisms let a team correct course without anyone feeling ambushed.

Is this a substitute for a lawyer, or preparation for meeting one?

Preparation, and the distinction is stated openly. Most published material on this subject is written to make founders feel they cannot take a step without counsel, which leaves them paying for a template they still do not understand. The session tells founders which decisions are theirs to make and which genuinely need professional drafting, so the meeting is shorter and far more useful.

Do you cover employee options and how the pool dilutes founders when investors come in?

Yes, and putting both halves in one session is deliberate. Founder shares and employee options are usually taught by entirely different specialists, so nobody sees the whole cap table at once. The lecture connects them, including where the option pool comes from in a funding round and what it costs the founders in practice.

Who this lecture is for

Aimed at founders and chief executives of post-MVP companies approaching the move to a professional management layer, and at human resources, learning and organisational development managers inside technology companies that grew fast and now feel the process gap. Executive forums and management teams book it for an offsite, and venture fund and accelerator platform teams run it across a portfolio of founders crossing from build to scale. Established non-technology companies launching their first digital product hit the same wall and belong in the room too.

Questions about this lecture

Is this about growth mindset or about concrete operating mechanics such as processes, metrics and organisational design?

Mechanics. The corporate lecture market treats growth as an inspiration topic, which is why executives keep booking motivating sessions and returning to the same bottlenecks the following week. This one deals with where decisions actually sit, which of them have to be written down, what gets measured across product, sales and finance, and how the structure changes as headcount does.

Do you cover the growth versus profitability decision, and do you give criteria for choosing?

Yes, with criteria rather than a preference. Most commentary names this as the big choice and then leaves the executive team to decide by instinct, which in practice means echoing whichever one the last funding conversation favoured. The lecture sets out what each path demands of the company operationally, so the decision is made once, on purpose, and communicated the same way to everyone.

How do you address the improvisation culture that works brilliantly in a small team and breaks at scale?

Directly, and it is usually the part of the room that goes quiet. Improvisation is a genuine competitive advantage early and a genuine liability later, and nobody wants to be the person who names it. The session gives management a shared, non-accusatory way to talk about which improvisations to protect and which have already turned into risk.

Do you cover what a company should deliberately stop doing as it scales, not only what to add?

Yes, and it is the half that gets skipped everywhere else. Every vendor sells either more process or more spirit, so founders are left afraid that structure will kill whatever made them work. The lecture puts the trade-off on the table honestly, including what to protect deliberately and what to retire without ceremony.

Do you cover hiring the first professional managers over the original team?

Yes, including the resentment nobody plans for. Bringing experienced managers in above the people who built the thing is one of the most predictable sources of damage in a scaling company, and it is almost never discussed out loud before it happens. The session covers how to sequence it, how to explain it, and what to give the original team so the move does not read as a demotion.

Who this lecture is for

Built for accelerator and incubator programme managers filling the legal and financial slot in a cohort curriculum, regional small business agency branches and municipal business development centres running early-stage entrepreneur courses, and university and college entrepreneurship programmes and student venture clubs. Coworking spaces and founder communities that want practical rather than inspirational content book it directly. Social venture and nonprofit accelerators, where founders arrive with no commercial background at all, get a version that assumes nothing. Startup people and finance leads book it for early employees.

Questions about this lecture

Does this cover both the legal and the financial side, or do we need two separate speakers?

One session, both halves, which is the reason it exists. Law firms publish on the legal side, finance providers publish on the financial side, and a founder is left assembling two incomplete pictures. The lecture connects them at the points where they actually meet, structure and liability, contracts and revenue recognition, ownership of work and company value.

Is it aimed at pre-revenue startups, or is it the same material as a general small business finance workshop?

It is written for the startup stage specifically. General small business finance content is built around established operations with steady customers, and its worked examples are clinics and studios. None of that speaks to a pre-revenue venture with investors, a cap table and development spend, so this session starts from that reality instead.

What does the session say founders can handle themselves versus what genuinely requires a lawyer or an accountant?

It draws that line explicitly, which almost nothing else does. Content written to sell professional services has an obvious incentive to leave founders feeling helpless. Here founders learn which decisions are theirs, which documents they can read unaided, and exactly where professional drafting or professional judgement is worth paying for.

Do you cover ownership of work created by freelancers, co-founders and previous employers, or only registration?

Assignment gets the attention, because that is the failure mode that actually derails deals. Most published material treats intellectual property as registration and patents, while the thing that surfaces in due diligence is a contractor who was never asked to assign what they built. The session covers when that assignment has to happen and what it looks like when it was missed.

How is this different from the subsidised entrepreneurship courses our participants can already take?

Those courses are broad and general, covering business planning for anyone starting anything. This session is narrow and sequenced for the startup path, giving an order of operations, what to settle before incorporating, before the first hire, before the first customer contract and before the first investor conversation. It complements a general course rather than repeating it.