Strategic Priorities | Renatus
PLANNING STRATEGIC PRIORITIES
Prepared for Demo · 07 Jul 2026

Strategic Priorities: 90-Day Focus

Three committed priorities — sales motion, onboarding productisation, and NDIS claiming automation — but the founder's willingness to actually let go of sales is the variable that determines whether any of them land.

The business is operationally strong where it counts — retention, product quality, and referral economics are all working. The problem is structural, not competitive: the founder is the single point of failure across sales, product decisions, and customer relationships, and the platform's architecture reflects the same pattern — bespoke everywhere, no templates, no leverage. AlliedCo did not churn because the product was bad; it churned because the enterprise capability the customer needed was never finished, and the person who might have saved the relationship was too stretched to act. The NDIS deadline changes the calculus entirely. A six-month window to automate new claiming rules is not a product roadmap item — it is a strategic forcing function.

The platform that ships NDIS compliance first will inherit a switching-cost advantage across hundreds of clinics simultaneously. Parking the enterprise decision is the right call — chasing multi-site chains is what created the overstretch in the first place, and the SMB retention moat is worth more at this stage than a second AlliedCo. The next 90 days are not about doing more — they are about stopping enough to do three things well. The founder's genuine commitment to exit the sales critical path is the single variable that determines whether the plan holds.

Where you are

The business is a practice-management platform serving 1,100 independent physio and allied-health clinics across Australia and New Zealand, generating $4.2m ARR with a team of 34. Two weeks ago, the single largest customer — AlliedCo, a 22-site chain — churned to a competitor's enterprise product, removing $310k ARR in one event. That is a 7.4% revenue loss in a single churn event, which is significant not just financially but as a signal: the platform's feature set was not sufficient to retain a customer at the enterprise end of the market. The more pressing force, however, is structural. The NDIS — Australia's National Disability Insurance Scheme — is changing its claiming and pricing rules in approximately six months.
Every clinic on the platform that handles NDIS participants will face compliance pressure, and the vendor that automates the new claiming flow first will have a defensible advantage. This creates a hard choice: pursue enterprise replacements for AlliedCo, protect and grow the SMB base, or prioritise the NDIS product build. All three are urgent. None can be done simultaneously at the quality level required with the current team and bandwidth.

What's working

Claiming Workflow:
The claiming workflow is the platform's sharpest competitive edge. Clinics report saving an hour of front-desk time per day — a tangible, measurable outcome that directly reduces one of the biggest operational costs in a small clinic. This is the feature customers stay for, and it should be protected and deepened before competitors can close the gap, particularly as NDIS rule changes make automated claiming more critical than ever.
SMB Retention:
Net revenue retention of 112% on the single-site and small-clinic segment means the existing base is not just staying — it is expanding. This is the financial engine of the business right now. It should be protected by maintaining product quality and support for this segment, and not cannibalised by resources redirected toward enterprise or product rebuilds.

Association Referral Channel:
Three state physio associations actively recommend the platform to their members, driving approximately 40% of new signups with near-zero customer acquisition cost. This channel is rare and hard to replicate — it is built on trust, not spend. It should be maintained through continued engagement with association partners and protected from any reputational risk that could follow a botched product transition.

Clinician-Led Product Roadmap:
Two senior clinicians embedded in the team shape what gets built. The result is a product that solves real clinical workflows rather than assumed ones — and it shows in retention. This should be accelerated: these clinicians should be central to any NDIS compliance build, since they will know what the new claiming flow needs to do in practice before the rules are even published.

Shipping Velocity:
Weekly shipping cycles in a regulated clinical market is a genuine structural advantage. Most competitors in this category move quarterly or slower. Zero regrettable attrition in 18 months means the team generating this output is stable. This pace should be protected — any strategic pivot must be sized to what this team can absorb without breaking the rhythm that makes the platform competitive.

What's draining you

Founder-Dependent Sales:
Every deal above $15k ACV runs through one person. This throttles pipeline to whatever the founder's calendar allows, and it means large accounts are fragile — when attention is elsewhere, they churn or never close. AlliedCo was not a product failure; it was a capacity failure. Fix: document the sales motion that actually works, cap the number of enterprise deals in flight at any one time, and hire or develop someone who can run 70–80% of the motion independently.
Bespoke Onboarding:
Three to five weeks of hand-built, bespoke clinic setup per customer is burning the implementation team and creating a hard ceiling on growth. The current model means every new customer is a custom project — and there is no template to delegate to. Fix: audit the last 20 onboardings, identify the 80% that is identical across setups, and build a standard template. Reduce bespoke work to genuine edge cases only.

Unfinished Enterprise Tier:
The half-built Enterprise tier is the worst of both worlds: too complex for self-serve, not complete enough to retain a sophisticated buyer like AlliedCo. It is consuming development attention without generating revenue or retention. Fix: make a binary decision — either resource it properly and finish it in one sprint cycle, or officially deprecate it and redirect those customers to a partner or a future roadmap commitment. Leaving it half-finished is the most expensive option.

Free Legacy Tier:
Approximately 200 clinics on a free legacy tier generate zero revenue but consume a material share of support time. This is a subsidy the business can no longer afford, particularly with a NDIS build on the horizon. Fix: set a sunset date, offer a migration path to a paid tier with a time-limited discount, and close the free tier. Some will churn — that is the correct outcome.

SWOT

SStrengths
Claiming workflow saves clinics one hour of front-desk time per day — the most cited reason customers stay and the hardest feature to replicate.
112% net revenue retention on single-site and small clinics means the SMB base is expanding without additional acquisition spend.
Three state physio associations recommend the platform to members, driving 40% of new signups at near-zero customer acquisition cost.
Two senior clinicians on staff shape the product roadmap, producing features that match real clinical workflows rather than assumed ones.
Weekly shipping cadence with zero regrettable attrition in 18 months — a stable, fast-moving team in a category where competitors move quarterly.
WWeaknesses
All enterprise sales above $15k ACV depend on the founder personally — pipeline is capped by one calendar and large accounts are structurally fragile.
Onboarding is entirely bespoke, taking three to five weeks per clinic with no template — unscalable and burning the implementation team.
The Enterprise tier is half-finished: too complex for self-serve, not complete enough to retain sophisticated multi-site buyers.
200 legacy free-tier clinics generate no revenue but consume significant support capacity that could be redirected to paying customers.
OOpportunities
NDIS claiming rule changes in six months create a hard compliance deadline — the first platform to automate the new flow gains a defensible switching-cost advantage across the entire clinic base.
The 112% NRR on SMB suggests untapped expansion revenue within the existing base through seat growth, add-ons, or tier upgrades.
Association referral channel could be deepened — formal partnership agreements or co-branded NDIS compliance resources could accelerate signups ahead of the rule change.
Sunsetting the free tier and converting even 30–40% to paid would add material ARR with no new customer acquisition required.
TThreats
Competitors targeting the same NDIS compliance window with faster or better-resourced engineering teams could make the platform's claiming workflow obsolete within six months.
A second large enterprise churn event before a replacement pipeline is built would compound the AlliedCo revenue loss and signal product-market fit risk to the market.
Founder burnout or sales capacity failure — if the one person closing enterprise deals is also managing NDIS build decisions and SMB retention, execution quality across all three will degrade.
Regulatory risk: if the NDIS build is delayed or built to the wrong spec, the platform could face a compliance gap that erodes trust with association referral partners.
S + O — Offensive
Use the clinician-led product team and weekly shipping velocity to complete NDIS claiming automation before the six-month deadline — and use the association channel to announce it early, converting compliance anxiety into acquisition momentum.
W + T — Defensive
Cap founder involvement in enterprise sales to avoid another AlliedCo scenario, and deprecate the free legacy tier to free up support capacity before the NDIS transition creates a second surge in support demand.
W + O — Building
Build a standard onboarding template using the last 20 clinic setups as the blueprint — then use the time saved to run a structured migration campaign converting legacy free-tier clinics to paid before the NDIS changes make the platform more valuable.
S + T — Protective
Protect the claiming workflow's lead by making NDIS automation a non-negotiable 90-day commitment — the 112% SMB retention depends on the platform remaining best-in-class on the feature clinics value most.

Your priority list

Productise Onboarding
144
Build Repeatable Sales Motion
63
Decide on Enterprise Tier
34
Priority Reach Impact Confidence Effort Score
Productise Onboarding
Audit the last 20 clinic setups, extract the 80% that is identical, and build a standard template that reduces setup time from 3–5 weeks to under one week. Frees the implementation team from perpetual bespoke work and creates the operational leverage needed to grow without burning the team.
9 8 8 4 144
Build Repeatable Sales Motion
Hire a sales lead and document the sales process that has worked — pricing, objection handling, demo flow, close triggers. Goal is one person running 70–80% of the motion independently within 90 days so pipeline is no longer capped by the founder's calendar.
6 9 7 6 63
Decide on Enterprise Tier
Make a binary, time-boxed decision: either commit the engineering resources to finish the enterprise tier in a defined sprint cycle, or officially deprecate it and redirect multi-site prospects to a partner or a future roadmap commitment. Leaving it half-built is the most expensive outcome — it consumes development attention and loses sophisticated buyers.
4 7 6 5 34
Productising onboarding scores highest because it touches every new customer, frees the implementation team immediately, and creates the operational floor the other two priorities depend on. A repeatable sales motion built on top of a broken onboarding process just accelerates the bottleneck — new deals close faster but stack up behind a 3-week bespoke setup queue. Fix the throughput constraint first, then build the pipeline. The enterprise tier decision is genuinely urgent but lower RICE because its reach is narrow relative to the SMB base — and it can be resolved with a single decision meeting rather than sustained execution. Score it as a forced choice, not a build.

What gets in the way

The obstacles most likely to prevent the priorities above from landing. In your conversation with Ren, you surfaced these as the constraints to manage, not just acknowledge.

The founder has not genuinely committed to removing himself from the sales process. Every deal above $15k ACV still runs through one person — not because no one else can learn the motion, but because control and relationship ownership have not been deliberately transferred. AlliedCo was not lost because the product failed; it was lost because the person who might have intervened was too stretched. Until the founder makes a real decision to hand over deal execution — not just hire someone to assist — the sales bottleneck will survive any hire.
high
Mitigation
Set a hard rule before the sales lead starts: the founder is available for one touchpoint per deal maximum — intro call or final close, not both. Document that constraint before the hire, not after.
Cash does not cover a sales hire and onboarding headcount simultaneously at current burn. This is a real sequencing constraint, not just a priority question. Choosing both means one will be underfunded — and an underfunded sales hire in a thin talent market is likely to fail within 90 days, compounding the cost.
high
Mitigation
Decide which hire comes first based on which bottleneck is costing more per month right now. The free legacy tier migration — if executed in the next 30 days — could add meaningful ARR before either hire lands, partially funding the sequence.
Senior GTM talent with allied-health SaaS experience in Australia is genuinely scarce. The last search took months. A 90-day commitment to a sales hire is optimistic if the search starts from scratch today.
medium
Mitigation
Start the search immediately — this week, not after onboarding is fixed. Consider a fractional sales lead for the first 60 days while the permanent search runs. Fractional narrows the talent pool less severely and keeps pipeline moving.
The NDIS claiming build competes directly for the same engineering bandwidth as onboarding productisation. Both require the implementation and product teams. Committing to both in 90 days without a clear resource split risks delivering neither to the standard required — particularly given the six-month compliance deadline is hard.
medium
Mitigation
Assign one named engineer or clinician as the NDIS lead from day one. Onboarding productisation should be scoped to the implementation team independently. The two builds must not share a single critical-path resource.

Your priorities

Priority 1: Build a Repeatable Sales Motion:
Hire a sales lead and document the motion that has worked — pricing, objection handling, demo flow, close triggers. The founder's first and only constraint: one touchpoint per deal maximum, set before the hire starts, not negotiated after. First action: open the search this week, and set the rule in writing before the first candidate is interviewed.
Priority 2: Productise Onboarding:
Audit the last 20 clinic setups, extract the 80% that is identical, and build a standard template that brings setup time from 3 – 5 weeks to under one week. This is an implementation team project that does not require the founder's bandwidth — which is exactly why it can run in parallel with the sales hire. First action: assign one implementation team member as owner and set a two-week deadline for the audit.

Priority 3: NDIS Claiming Automation:
Get ahead of the six-month compliance clock by building claiming automation for the new NDIS rules before competitors do. This is the retention moat — the reason 1,100 SMB clinics cannot leave before the deadline hits. The clinician-led product team is the right group to lead this build. First action: assign a named NDIS lead from the product team this week and confirm they share no critical-path resources with the onboarding build.
About About this report

What this is. This Strategic Priorities was built through a guided conversation between Demo and Ren.

How it was built. All analysis reflects your own thinking — structured using established frameworks, sharpened, and presented clearly.

This report was produced by Ren, an AI advisor built by Renatus. It is based on information you provided during the conversation and established frameworks. It is intended to support — not replace — your own judgement. All conclusions should be reviewed before acting on them.

Renatus applies the underlying principles of established methods and credits their origin where relevant. Named frameworks, methods, and instruments are the property of their respective owners. Reference to them does not imply endorsement or affiliation.

Frameworks Guided Strategy Used

3 frameworks were used to structure your thinking:

SWOT Analysis Maps your strategic position across four dimensions — internal strengths and weaknesses you control, and external opportunities and threats you respond to. The foundation for all strategic priority work that follows. Emerged from Stanford Research Institute in the 1960s.
TOWS Matrix Takes the items from your SWOT and combines them to identify strategic moves. Each intersection type points to a different kind of action — offensive moves that use strengths to capture opportunities, defensive moves that use strengths to mitigate threats, building moves that address weaknesses to pursue opportunities, and survival moves that minimise weaknesses before threats exploit them. Developed by Heinz Weihrich in 1982.
RICE Scoring Scores each priority candidate across four factors — Reach (how many people or outcomes it affects), Impact (how significantly it changes performance), Confidence (how certain you are it will work), and Effort (the resources it requires). Formula: (Reach × Impact × Confidence) ÷ Effort. Makes trade-offs visible so the choice of priorities is based on evidence, not gut feel. Developed at Intercom and widely adopted in product and strategy work.
Meet Ren
Your AI strategist
We use essential cookies to keep you logged in and protect your session. Our only optional cookies remember your language preference — we don't track you or collect unnecessary data. Cookie Policy · Privacy Policy

Cookie Settings

Choose which cookies you'd like to allow. Essential cookies cannot be disabled as they are required for the platform to function.

Essential Cookies Always Active
Login sessions, security tokens, and consent preferences. Required for the platform to work.
Functional Cookies
Language preferences, display settings, and last accessed report. Disabling may affect personalisation.
Analytics Cookies
Aggregated, anonymised usage data to help improve the platform. Never used to identify you personally.