We have run an advisory program at StartPro for a little over two years. The mechanic is simple: a founder books a recurring session — usually monthly, sometimes weekly during a specific stretch — and we work through whatever the founder needs that week. Some sessions are strategy. Some are financial modelling. A surprising number are a quiet thirty minutes of the founder talking out loud.
Twenty-six founders have come through the program. They build different things — health-tech, real-estate-tech, fintech, education, climate. They come in at different stages — pre-revenue, post-revenue, post-Series-A. They are local and international. And the bottleneck they hit is, almost always, the same one.
It is not the product. The product is usually good enough to test. It is not the market. The market is usually addressable. It is not the funding. Most of these founders have raised what they need to ship the next milestone.
The bottleneck is the founder's allocation of their own week.
What that actually looks like.
A founder, six months in, with a product live and three to five paying customers. They are working seventy hours a week. They are tired. When we sit down and walk through the actual calendar from the past four weeks, the pattern is the same one almost every time.
About a third of their hours are on operations they no longer need to be doing — onboarding, support, invoicing, content scheduling, low-level meetings they were not the right person for. About a quarter of the hours are reactive — answering emails, putting out small fires, attending meetings they accepted because it felt impolite to decline. The remaining hours are the actual work: building, selling, fundraising, hiring. The high-leverage work usually fits in fewer than fifteen hours a week. Sometimes ten.
The founder can describe the high-leverage hours when asked. They know what they should be doing more of. They just are not doing it, because the other hours are louder.
Why this is the bottleneck.
A founder who is working seventy hours a week with fifteen of those on high-leverage work is, mathematically, a founder working a fifteen-hour week. The hours are not the constraint. The allocation is.
This is not a productivity problem. It is not solved by more discipline, a better calendar app, or a productivity book.
The founders who are stuck on this bottleneck are usually high-discipline people, often higher-discipline than I am. They are stuck because they have not made one specific decision yet: which of the operations they currently do is the next one they will stop doing themselves.
What the unblock usually looks like.
Most of the time, the unblock is a single hire — a junior operations person, often part-time, who absorbs the support / onboarding / scheduling layer that the founder is doing. Sometimes the unblock is an existing teammate the founder hadn't yet asked. Sometimes it is a contractor, weekly.
It is almost never a "Chief of Staff" or a "VP of Operations." Those are the labels of a later stage. At this stage the unblock is "the first person whose job is to make Wednesday afternoon disappear for me."
The math is brutal. A junior ops hire at $50,000 a year, doing twenty hours a week of work the founder is doing, returns one full day per week to the founder. If the founder uses that day on a sales conversation that lands one $50,000 contract per year, the hire has paid for itself in the first quarter. If the founder uses it on fundraising and the round closes a month sooner, the math is even clearer.
What founders resist, often, is not the math. They resist the act of admitting that the founder cannot personally do everything. The act of writing the job description is the unblock. The hire is just paperwork.
Why founders don't see it themselves.
Three reasons, in roughly the order I see them.
One: identity. Many founders started the venture because they liked doing the work that is now eating their week. The customer support is satisfying. The hands-on operations are familiar. Letting go feels like a downgrade of their own role, even when it is the opposite.
Two: standards. The founder believes — often correctly — that they do the work better than anyone they could hire at this stage. So they keep doing it. The math is right at the per-task level. It is wrong at the per-week level.
Three: cost. Most early founders are still in the bootstrapping mindset where every dollar is examined. A part-time ops hire feels expensive. A part-time founder, valued at the founder's actual market rate, is much more expensive.
We talk about all three. The one that lands varies by founder. Identity is the hardest. The founders who unblock most quickly are the ones who realize their identity is "the person who decides what gets built," not "the person who does every task themselves."
What we don't tell them.
We do not tell founders to hire a Chief of Staff. We do not tell them to read a productivity book. We do not tell them to "delegate more" in the abstract. Those instructions don't land.
What we do is sit with the founder and walk through one week of calendar. We pick one specific recurring item — usually customer onboarding calls, or scheduling, or invoice follow-up — and we write the job description for the person who will take that item. By the end of a session, the founder has a job description, a budget, and a deadline for posting the role.
If the founder is still doing the same task four weeks later, we talk about identity, not productivity.
The hours are not the constraint. The allocation is.
This is the work I most enjoy, honestly. There is something quiet about it. The founder has already done the hard part — they have built a thing that someone is paying for. The bottleneck is, by then, the founder themselves. The advice that helps is not the advice that's loudest in startup-Twitter. It is the advice that gives them their Wednesday afternoon back.
If you are a founder six months into a working product and you want a candid hour on your calendar, write to info@startpro.ca. The advisory program is by application; we take a small number of founders at a time on purpose.
— K.