The Practitioner Economics

The actual reason to become an SDC Certified Practitioner.

Most consulting credentials sell you a logo and access to a community. This one sells you a business model. The credential is the entry ticket; the business model is what makes the ticket worth more than its price.

This document explains how the SDC ecosystem changes the economics of independent practice — for the practitioner, for the client, and for Axius SDC. The short version: it is positive-sum on every axis, and the practitioner who understands the compounding gets to a stable, recurring six-figure practice in 18-24 months on substantially fewer billable hours than traditional consulting requires.

The two compounding axes

What makes SDC structurally different from every other consulting model is that your work compounds in two independent directions at once.

Axis 1: Component reuse across engagements in a vertical

The first time you onboard a healthcare physical therapy clinic, you do real work. You introspect their EHR, their billing system, their scheduling tool. You approve component assemblies. You mint new components for the things that don't already exist in the catalog. You generate the bespoke application. The practitioner labor is meaningful — say 60-80 hours over 6 weeks.

The second PT clinic has substantially the same data shapes. Same EHR vendor (or one of three common ones). Same billing concepts. Same scheduling primitives. The components you minted for clinic #1 — PatientEncounter, TherapyPlan, InsuranceClaim, AppointmentSlot — are reused. They're already in the catalog, they cost nothing to deploy, and they bring their constraints, validators, and identifiers with them.

Your labor for clinic #2 might be 30-40 hours instead of 60-80. By clinic #5, you're at 15-20 hours. By clinic #10 in the same vertical, you're at 8-12 hours of practitioner labor for an engagement you can still bill at $25,000-$35,000.

The component library you've built is private to your practice in the sense that you developed it, you understand the vertical, and you have the client relationships. A competitor entering the same vertical from scratch would have to do all the same first-engagement work. Your library is a moat that grows every time you use it.

Why this works at all is the minimum knowledge modeling principle (Module 1 §1.6). Your PatientEncounter component is reusable across every PT clinic precisely because it captures only what makes an encounter an encounter and distinguishes it from nearby concepts — not every possible attribute that any clinic anywhere might want to record. The local variations (this clinic uses a specific intake questionnaire, that clinic tracks a custom outcome score) are captured by composing additional minimum components at use time, not by inflating the core component. A maximal PatientEncounter with 200 optional fields would be over-fit to its first client and wouldn't transfer cleanly. A minimum PatientEncounter transfers everywhere. The compounding is downstream of the modeling discipline.

Axis 2: Recurring touches within a single client over time

This is the part that surprises practitioners coming from project-based consulting, and it's the part that turns a one-time engagement into a perpetual revenue stream.

A client's data does not stand still. New fields appear in their CRM. A new partner integration requires a new datasource. A regulatory update changes what they need to capture. A business line is added. A merger brings in new systems. A product launch creates new entity types.

In traditional consulting, each of these triggers a small project, a scope conversation, and a fresh engagement letter. The friction is real and the practitioner often eats it for relationship reasons.

In the SDC ecosystem, each of these triggers a touch:

1. The practitioner runs SDC Agents SMB introspection remotely against the changed datasource (15-30 minutes)
2. The delta is reviewed; new components (if any) are minted via SDCStudio (5-15 minutes)
3. The updated data model and application bundle are downloaded (automatic)
4. The practitioner imports the new app, asks the LLM to regenerate the UI bindings (10-30 minutes)
5. The redeployed application is shipped to the client (15 minutes)

Total practitioner labor per touch: 30 minutes to 4 hours depending on complexity. Most touches are at the lower end. The deliverable is a redeployed application running on the client's own infrastructure, ready for use the same business day.

Practitioners bill per touch, not per hour. A typical touch is $1,500 - $3,000. Most clients have 4-12 touches per year as their environment evolves. A portfolio of 20 such clients is 80-240 touches per year of recurring revenue with mostly-remote, mostly-short labor.

Neither axis dilutes the other. They compound together.

A worked example

Meet Sarah. Sarah is a fictional but plausible practitioner. She is a 40-year-old former data engineer who decided two years ago to leave a Fortune-500 job and start an independent practice. She picked outpatient mental health practices as her vertical because she has a personal connection to the space and she noticed that small mental health groups are underserved by data tooling.

Sarah took the SDC certification in March. Her three years of practice numbers below are conservative — she could do better with more aggressive recruiting, or worse if she fails to focus.

Year 1

Add ~80 hours of learning, business development, and operations overhead → ~250 total hours.

Year 1 effective hourly rate: ~$546/hour blended. Compare to a traditional consultant billing at $200/hour for 1,500 hours = $300K but with no compounding for next year.

Year 2

Sarah now has a 4-client portfolio generating recurring touches and a small but real component library for mental health practices. Her library includes TherapySession, GroupSession, InsuranceAuthorization, PHIRedaction, SlidingScalePayment, and a dozen others. New engagements in the same vertical reuse most of these.

~80 hours overhead → ~250 total hours.

Year 2 effective hourly rate: ~$936/hour blended.

Note: Sarah's total hours did not increase from Year 1. Her revenue grew 71%. That is the compounding showing up in the numbers.

Year 3

~100 hours overhead → ~320 total hours.

Year 3 effective hourly rate: ~$1,113/hour blended.

Sarah now runs a $356K/year practice on roughly 6 hours of work per week. She is not "working harder than a real job"; she is working substantially less than a real job and earning more than she did at the Fortune 500. Her primary constraint is not labor, it is recruitment of new clients in her vertical — and the recruitment is easier every year because she has a growing public reputation in mental-health practice circles.

What Sarah is not doing

• Sarah is not coding 40 hours a week. The SDC ecosystem does the schema work; her job is judgment, client relationships, and the 30-minute touches.
• Sarah is not selling SaaS. Her clients own their applications and run them on hardware they bought from a local shop.
• Sarah is not on call. The clients call her when they want to change something, not when their system breaks.
• Sarah is not building a team. She is a solo practitioner with a vertical library. If she wanted to scale further she could hire a junior practitioner, but the model works at solo scale.
• Sarah is not relying on referrals from a brand. Her practice is built on her own reputation in her own vertical, with her own client relationships.

Why this is positive-sum

For the practitioner

• Recurring revenue per client without recurring labor cost
• Compounding component library that grows in value over time
• Effective hourly rate that increases each year as compounding kicks in
• Solo-scalable to a healthy six-figure practice
• No vendor exclusivity, no commission structure, no quotas
• The credential is portable; the library is proprietary; the relationships are personal

For the client

• A bespoke application running on their own infrastructure (not a SaaS subscription)
• A trusted single point of contact who knows their data deeply
• Predictable cost: pay per touch when something actually changes, not on a calendar
• No forced software upgrades. SaaS vendors upgrade on their schedule, not yours — and every upgrade risks breaking integrations, retraining users, and re-validating workflows. Your client's bespoke application changes only when they ask for a change, on their timeline.
• No data migrations, ever. Every SaaS migration loses something: history, customizations, edge-case records, attached documents. Your client's data lives in their environment from day one and never moves. New schemas evolve in place; old data is upgraded by the same touch that updates the application.
• No vendor lock-in: the schemas, the apps, the data, all theirs
• Audit-ready provenance and constraints baked in from day one
• Total cost of ownership over 5 years is materially lower than the SaaS alternative

The "no forced upgrades, no migrations" point is the one clients return to most often unprompted. Most have personally lived through a forced SaaS migration that lost data or broke a workflow they depended on. They will never forget that experience. When you offer them a model where it cannot happen again, they become long-term clients and active referral sources. Practitioner satisfaction is downstream of client satisfaction, and client satisfaction is downstream of "the data infrastructure has not betrayed me in three years."

For Axius SDC

• Distribution at SMB scale that direct sales cannot economically reach
• Every practitioner touch generates a small SDCStudio fee for component minting and app downloads
• Aggregate revenue scales with the number of practitioners and the number of their clients and the frequency of their touches — three multiplicative axes
• Aligned incentive: Axius SDC wins when practitioners win, not when practitioners are extracted from
• The ecosystem improves with every component minted, because the catalog grows and benefits the next practitioner
• Open standards (Apache 2.0, W3C, ISO, FAIR) keep the moat structural rather than legal

There is no one in this picture who is being extracted from. That is unusual for a software-driven consulting model and it is the reason the program is structured the way it is.

When this model does not work

It would be dishonest to leave this section out.

This model does not work for practitioners who... - ...are not willing to focus on one or two verticals. The compounding requires concentration. A generalist who does one healthcare client, one law firm, and one manufacturer in their first year captures none of the axis-1 compounding and has a much harder Year 2. - ...want to scale primarily by hiring. The model works at solo scale. It can support a junior associate, but the leverage is in compounding, not headcount. If your goal is to build a 50-person consultancy, this is not your model. - ...need predictable monthly income from day one. Year 1 is real work for real money but it is project-shaped, not retainer-shaped. The recurring touch revenue takes 12-18 months to become a meaningful share of the income. - ...are uncomfortable with the LLM-assisted parts of the workflow. The 30-minute touches assume you are fluent in driving an LLM to regenerate UI bindings against the new model. Practitioners who insist on hand-coding every UI change will not see the per-touch labor numbers in this document.

This model does not work for clients who... - ...want a SaaS subscription with a vendor's brand on it. They should buy the SaaS. - ...have no operational data to model. They should ship a product first and come back later. - ...are about to be acquired. The work would be thrown away. A scoped data cleanup is the right alternative.

This model does not work for Axius SDC at... - ...the scale of a few dozen practitioners. The aggregate touch revenue is real but small until the population grows. The first 18-24 months of the program are an investment in the population, not a revenue line.

The honesty about where this fails is part of what makes the model trustworthy.

How to start

If the math above resonated, the path is short:

1. Pick a vertical you have credibility in — a sector you have worked in, served as a client, or have personal connection to. The compounding requires focus.
2. Create your SDCStudio account and fund your wallet with the $10 minimum at sdcstudio.axius-sdc.com. The $10 stays yours and is used for component minting on your first engagement. This is the only registration step.
3. Open the "Practitioner Curriculum" item in your SDCStudio user menu (it appears automatically once your wallet is funded). Read the framework, browse the seven curriculum modules, run the Module 6 hands-on lab.
4. Click "Request Certification Exam" in the same menu when you are ready. The program administrator schedules your 90-minute exam window.
5. Pass the exam. An SDCStudio admin applies an additional $100 credit to your already-funded wallet, marks you as a Certified Practitioner, and adds you to the public directory.
6. Find your first client — probably someone you already know, in the vertical you picked.

The program does not guarantee Sarah's numbers. It guarantees that the mechanism is in place and the components are available and the credential is real. The numbers depend on you doing the focused, vertical-specific work that makes the compounding compound.

A final note on numbers

The numbers in the Sarah example are deliberately conservative. They assume: - Average engagement fee in the lower half of the $25K-$60K range - Average per-touch fee of $2,000-$2,200 (Module 5 suggests $1,500-$3,000) - A 4-client first year (Sarah could plausibly do 5-6 with focused recruiting) - A modest 60% utilization on billable activity

A practitioner who runs at the high end of every assumption could plausibly reach $500K+ in Year 3. A practitioner who runs at the low end will reach $200K in Year 3, which is still substantially better than most independent consulting alternatives.

The numbers you actually achieve depend on: - Vertical focus (concentrated > scattered) - Client retention (recurring touches require relationship work) - Recruitment cadence (the credential gets you in the door; the relationships keep you there) - Discipline about pricing (don't underprice your fifth engagement just because it cost you nothing to deliver)

Module 5 (Prescribing Interventions) and Module 7 (Building Proposals) cover the practical pricing and engagement skills. The economics in this document are what the curriculum is for.

The SDC Certified Practitioner program is operated by Axius SDC, Inc. The framework, curriculum, and templates are licensed under Apache 2.0. The economic model is not. The model belongs to whoever has the discipline to execute it.