We use cookies for privacy-respecting analytics to improve this site.
You can opt out anytime. See our
Privacy Policy.
The CTGA Framework Methodology
Operations maturity, scored.
The Helix Score is a credit score for how your business runs.
One number from 100 to 900, rolling up four pillars (Controls, Technology, Growth, Adoption) into a figure you
can put on a board update, track quarter over quarter, and use as the baseline for
everything you fix next.
That sentence is the whole framework. The rest of this page explains how the number gets
made, what the bands mean, and what you do with it.
What is the CTGA Framework?
The CTGA Framework is a proprietary operations maturity model built by Helix Stax for
small and mid-market businesses. CTGA stands for Controls, Technology, Growth, and
Adoption -- the four pillars the framework scores. Controls covers financial and process
discipline. Technology covers the actual software stack and how well it fits the business
model. Growth covers sales, marketing, and the systems that produce revenue. Adoption
covers whether the team uses what the business has paid for -- the failure mode where
companies spend $400,000 a year on software nobody opens. Each pillar rolls into a single
Helix Score between 100 and 900. Unlike CMMI-derived models that score on a five-level
ladder, the Helix Score is a continuous number designed to be comparable across quarters
and defensible to investors. The framework is delivered by Helix Stax through the free
call, a full CTGA Assessment, and an implementation retainer.
Each pillar carries its own definition, its own inclusion list, and its own list of
things it deliberately does not measure. Definition by
exclusion matters as much as definition by inclusion.
C
Controls
25%
weight
The Controls pillar measures the disciplines keeping a business legal, insurable, and audit-defensible. It scores compliance deadlines, vendor contracts, licensing currency, financial controls, documented procedures, and the records that prove all of it works when nobody is watching. Controls also covers the basic security posture an SMB needs -- MFA, backup discipline, the response plan for a real incident.
Controls does not measure regulatory strategy, cybersecurity at the enterprise threshold, or financial planning. It scores whether the rules you already say you follow are actually being followed. The most common Controls failure is "we have the policy and no enforcement" -- a written rule with no evidence anybody follows it. Controls is 25 percent of the Helix Score.
T
Technology
30%
weight
The Technology pillar measures the actual stack the business runs on. It scores the CRM, the phone system, file storage, the practice-management or vertical platform, accounting, integrations, per-seat licenses, and whether the stack fits the business model. Each tool is rated on configuration quality, integration health, and seat utilization. AI tooling lives inside Technology when the business has adopted it -- CTGA does not score "AI maturity" as a separate pillar.
Technology does not measure DevOps maturity, observability, or platform engineering. Those concerns belong to engineering organizations, not the 5-to-150-person service businesses CTGA was built for. The most common Technology failure is paying for seats nobody opens. Technology is 30 percent of the Helix Score -- the largest weight because the dollar surface is largest.
G
Growth
20%
weight
The Growth pillar measures the systems turning marketing spend into closed revenue. It scores lead capture, lead response time, qualification, conversion rates, retention, and the CRM hygiene behind all of it. Growth includes the front end (how prospects find the business) and the back end (how revenue is forecast, billed, and collected).
Growth does not measure marketing strategy, brand work, or pricing decisions. It measures whether the leads you already paid to get are converting at the rate they should. The most common Growth failure is the slow follow-up -- the average small business takes nearly two days to call a web lead, and a majority of web leads never get called at all. Growth is 20 percent of the Helix Score.
A
Adoption
25%
weight
The Adoption pillar measures whether the team actually uses what the business has paid for. It scores login rates, feature usage on the workflows that matter, the gap between trained users and active users, and the rate at which paid software seats produce business work. Adoption is where the other three pillars succeed or fail. A perfect Controls policy is worthless if nobody follows it. A perfect Technology stack is a subscription fee if nobody opens it.
Adoption does not measure user satisfaction, feature usage at the SKU level, or HR or culture broadly. The most common Adoption failure is the founder running a parallel system because the team's tool is too painful to use. Adoption is 25 percent of the Helix Score.
What is an operations maturity assessment?
An operations maturity assessment measures how well a business's controls, technology,
growth systems, and software adoption work together. Unlike IT-focused maturity models,
which score infrastructure and incident response, an operations maturity assessment scores
the full operating model -- financial controls, the technology stack, growth functions
like sales and marketing, and whether the team actually uses the tools the business has
paid for. Most assessments produce a score per dimension on a five-level scale. The CTGA
Framework, built by Helix Stax for small and mid-market businesses, rolls those dimensions
into a single Helix Score between 100 and 900. A score of 270 indicates basic functioning
with significant unused investment; a score of 700 indicates a mature, instrumented
operation that runs without founder dependence. The number is comparable quarter over
quarter, defensible to investors, and short enough to remember.
The Helix Score rolls those four pillars into one number from 100 to 900. Each pillar is
scored on two tracks -- Systems (the configured tools and
documented procedures) and People (whether your team uses
any of it) -- so the headline number sits on top of eight sub-scores. Most businesses score
between 250 and 400 on their first assessment. A score of 700 or above means the business runs
on systems instead of heroics. The number is comparable across quarters, short enough to remember,
and structured exactly like a credit score so the buyer's instinct about what bands mean is
correct from the first read.
The Helix Score is not a consumer credit report, a business
credit report, or an insurance underwriting score.
See the full regulatory disclaimer.
How do I score my business operations from 100 to 900?
The Helix Score is a single number between 100 and 900 that summarises a business's
operations maturity. It is produced by the CTGA Framework, which scores four pillars:
Controls (financial and process controls), Technology (the actual stack and how well it
fits the business), Growth (sales, marketing, and revenue systems), and Adoption
(whether the team uses what the business paid for). Each pillar contributes
proportionally to the final score. Most small businesses score between 200 and 400 on
their first assessment. The threshold for an "instrumented" operation -- one that runs
without founder dependence -- is approximately 650. The Helix Score is set by the
founder of Helix Stax, working from data the platform collects, rather than by a
software questionnaire or an averaged consultant panel. One accountable judgment, not a
committee average.
CTGA is delivered in three tiers. The retainer ends when your Helix Score moves to the
agreed band threshold -- not when a calendar runs out.
Free IT Assessment Call
Free
A free conversation with the founder of Helix Stax -- no intake form, no demo, no
pitch deck. The buyer walks out with the top three operational gaps named, an
estimated Helix Score band, and a plain-English summary of what's broken.
Core engagement
Full CTGA Assessment
Paid -- 7 days
The paid 7-day engagement producing the official Helix Score, the Helix Score Report
PDF, the priority-ranked gap list, and an optional 30-day implementation roadmap.
Implementation Retainer
Monthly -- band-targeted
The monthly engagement that closes the gaps the assessment named. The team closes
gaps, trains your staff, and re-scores quarterly. The retainer ends when your Helix
Score moves to the agreed band threshold, not when a calendar runs out.
How CTGA is different from CMMI
Most operations maturity frameworks inherit from the Capability Maturity Model Integration
scale developed at Carnegie Mellon -- five named levels, scored per dimension, used
heavily inside enterprise IT transformation programs. CTGA is structurally different in
three ways. First, it produces a single number from 100 to 900 instead of a per-dimension
ladder. Second, its four pillars match the buyer's own vocabulary (Controls, Technology,
Growth, Adoption) instead of the consultant's vocabulary (Defined, Managed, Optimized).
Third, the score is set by the founder of Helix Stax with the platform feeding the data --
one accountable judgment instead of a software questionnaire or a committee average. CTGA
was built for owner-operators of 5-to-150-person service businesses, not for Fortune 1000
transformation offices.
Figure 1 -- CMMI-derived models score on a discrete
five-level ladder per dimension. The CTGA Framework rolls four pillars into a single continuous
Helix Score from 100 to 900, with six named bands.
Figure 2 -- Operations maturity is broader than digital
maturity or IT maturity. A business can have high digital maturity (lots of digital tools)
and low operations maturity (controls weak, growth unmeasured, team doesn't use the tools).
Operations maturity vs digital maturity vs IT maturity
Digital maturity measures how well a business uses digital tools across the
organization. IT maturity measures how reliably the IT department runs services,
incidents, and infrastructure. Operations maturity is broader than either: it scores the
full operating model -- controls, technology, growth systems, and adoption -- against a
defined framework. A business can have high digital maturity (lots of digital tools) and
low operations maturity (nobody uses the tools, controls are weak, growth is
unmeasured). The CTGA Framework, used by Helix Stax, is an operations maturity model
rather than a digital or IT maturity model. It scores the four pillars on a 100-900
scale and produces a single Helix Score rather than the five-level ladder common to
CMMI-derived models. The distinction matters because the buyer for an operations
maturity assessment is usually the owner-operator or COO, not the CIO.
How is CTGA different from other maturity frameworks?
Most operations maturity frameworks -- Accenture's Intelligent Operations, PagerDuty's
Digital Operations Maturity Model, the CMMI-derived models -- score per dimension on a
five-level ladder (Reactive, Defined, Optimized, etc.). They were built for enterprise
IT or transformation programs. The CTGA Framework is different in three ways. First, it
produces a single Helix Score between 100 and 900 rather than a per-dimension ladder --
comparable across quarters, defensible to investors. Second, its four pillars (Controls,
Technology, Growth, Adoption) match how a small-business owner already thinks about the
company, rather than how a consultant categorises a transformation program. Third, the
score is set by the founder of Helix Stax, with the platform feeding the data -- one
accountable judgment rather than a software questionnaire or a committee average. That
judgment is shaped by a founder trained through Harvard and MIT programs, and a team with hands-on experience supporting enterprise environments like Xfinity. The framework was built for
owner-operators of 5-to-150-person service businesses, not for Fortune 1000
transformation offices.
The Helix Score lands in one of six bands. The band is the qualitative read on the
quantitative number -- what the score actually means about how the business runs day to
day. Most first-time scores land in Developing.
The six Helix Score bands, from Critical (100-249) to Optimal (850-900), with the
canonical descriptor for each band.
Band
Range
Label
What it means
1
100-249
Critical
Basic operations function, but the business is exposed. Compliance gaps are real. Software waste is high. Lead leakage is the norm. The team works around the systems instead of through them. Typical for businesses that grew faster than their infrastructure. The fix is straightforward and the payback clock is short.
2
250-399
Developing
The most common first-assessment band. The bones are in place. Some tools work, some don't. Some processes exist, some are tribal knowledge. Visible improvement happens in 90 days when the right gaps get prioritized -- usually the gap between what you bought and what your team uses.
3
400-549
Functional
The running-without-daily-emergencies band. Most tools are used by most of the team most of the time. Compliance is mostly current. Growth is measurable. The owner can take a week off without the business breaking. Next-band gains come from instrumentation -- turning "mostly" into "measurably."
4
550-699
Strong
The runs-on-systems-not-heroics band. The four pillars work together. Most of the team works through the tools, not around them. Compliance is documented and defensible. Lead response is fast. The owner is no longer the bottleneck. Next-band gains come from closing the last gaps that still depend on the founder being in the room.
5
700-849
Leading
A reference operation. The systems and the team are aligned. The owner is replaceable on any given day. Compliance is proactive. Software waste is below industry benchmarks. Lead response is sub-five-minute. The business can absorb growth without redesign. Most businesses in this band are preparing for acquisition, succession, or a step-change in scale.
6
850-900
Optimal
The rare top band. The business runs at the practical ceiling of what CTGA measures. Reaching it requires sustained investment in all four pillars. Most operations do not need to be here; this band is for businesses where operational quality is itself the competitive moat.
Pillar weights
The four pillars do not contribute equally to the Helix Score. Opacity on weights looks
defensive. Publishing them deliberately is part of why the score is credible.
Pillar weights for the CTGA Framework v2.1: Controls 25 percent, Technology 30
percent, Growth 20 percent, Adoption 25 percent.
Pillar
Weight
Why
Controls
25%
Binary-failure mode -- when Controls fails, it tends to fail catastrophically (audit finding, insurance non-renewal, regulatory action).
Technology
30%
Largest dollar surface area on the typical SMB balance sheet -- software is the second-largest controllable expense after payroll.
Growth
20%
Important but the most variable across business models; the weight is conservative until the corpus reveals the true distribution.
Adoption
25%
The amplifier -- Adoption is what determines whether the other three pillars produce returns or sit on a shelf.
The formula and the maturity scale
The Helix Score is produced by the formula below, operating over the weighted maturity
inputs gathered during a Full CTGA Assessment. The same maturity inputs, scored against
the same methodology version, will yield the same Helix Score forever.
HelixScore = 100 + ((Sum wi * Mi) / (Sum wi * Maxi)) * 800
where:
wi = the published weight of capability i
Mi = the observed maturity level of capability i (1-5)
Maxi = the maximum maturity level (always 5)
The formula is anchored at the floor of 100 and the ceiling of 900, normalized through
the ratio of weighted observed maturity to weighted maximum maturity, multiplied by the
800-point span, and added to the 100-point floor.
The capability model -- 40 engine capabilities, 25 rolled-up clusters
The CTGA scoring engine operates on 40 capabilities -- five
questions per pillar, per track (5 x 2 x 4 = 40). Each capability has a five-level rubric, a
published weight inside its pillar-and-track group, and a stable identity (e.g. C-systems-1). The 40 engine capabilities produce 40 capability scores, which roll into 8 track
sub-scores, which roll into 4 pillar scores, which roll into the single Helix Score. In
some buyer-facing surfaces the framework prints 25 rolled-up clusters instead of the 40 engine capabilities -- the engine is 40, the marketing layer is 25, and
the methodology page picks whichever serves the immediate clarity goal.
The 1-5 maturity scale
Every capability is scored on a 1-to-5 maturity scale. The same five-level ladder applies
to both the Systems track and the People track. Reconciling the two tracks to a single
scale is what makes the eight sub-scores comparable.
The canonical 1-to-5 maturity scale used across both Systems and People tracks:
Reactive, Developing, Defined, Managed, Optimized.
Level
Name
What it means
1
Reactive
Capability exists in name only. Activity happens when something breaks. No documented process, no consistent owner, no measurable outcome.
2
Developing
Capability has a basic shape. Some procedures written, some followed. Outcomes inconsistent. Recovery from incidents takes longer than it should.
3
Defined
Capability is documented and mostly followed. Outcomes meet baseline expectations. Improvement work happens when the team has time.
4
Managed
Capability is instrumented, measured, and reviewed. Outcomes are predictable. Continuous improvement is part of the operating rhythm.
5
Optimized
Capability is a competitive advantage. Outcomes exceed industry norms. The capability itself improves faster than the market changes.
Certain capabilities are critical enough that a maturity level of 1 caps the overall Helix
Score regardless of what the rest of the inputs say -- see the critical-floor mechanism
documented in the architecture spec. Every Helix Score is stamped with a methodology
version (v2.1.0 at ship). The appeal path is documented at /legal/helix-score-disclaimer.
Questions
Frequently asked questions about Helix Stax managed IT services
The Helix Score runs from 100 to 900 and is produced by a weighted formula: HelixScore = 100 + ((Sum wi x Mi) / (Sum wi x Maxi)) x 800. The scoring engine operates on 40 capabilities, five per pillar per track. Each capability is scored 1 to 5 on a maturity rubric. Those 40 capability scores roll into eight track sub-scores, then into four pillar scores, then into the single Helix Score. Pillar weights are published: Technology carries 30 percent, Controls 25 percent, Adoption 25 percent, and Growth 20 percent. Some capabilities are designated critical-floor: a maturity level of 1 on any of them caps the overall Helix Score regardless of performance elsewhere. Every score is stamped with a methodology version (currently v2.1.0), so the same inputs produce the same score across reassessments.
Controls (25 percent of the Helix Score) measures the disciplines keeping a business legal, insurable, and audit-defensible: compliance currency, financial controls, documented procedures, and security basics like MFA and backup discipline. Technology (30 percent) measures the actual software stack, rated on configuration quality and seat utilization. It carries the highest weight because software is the second-largest controllable expense after payroll. Growth (20 percent) measures the systems turning marketing spend into closed revenue: lead capture, response time, conversion rates, and CRM hygiene. Adoption (25 percent) measures whether the team actually uses what the business has paid for: login rates, feature usage, and the gap between trained users and active users. The most common Adoption failure is a founder running a parallel system because the team tool is too painful to use.
Every pillar in CTGA is scored on two parallel tracks: Systems and People. The Systems track scores configured tools and documented procedures, the evidence side of the pillar. The People track scores whether the team actually uses those systems, the behavior side. Each pillar produces two sub-scores, one per track, for a total of eight sub-scores across all four pillars. The 40 capabilities in the scoring engine break down as five questions per pillar per track (5 x 2 x 4 = 40). The two-track structure is what surfaces the most common gap: a business with a strong Systems score and a weak People score has built the foundation but not the habit. The Helix Score headline number sits on top of all eight sub-scores, which is why two businesses with identical headline scores can have very different operational profiles underneath.
The score lands in one of six named bands. Critical (100-249): the business is exposed, compliance gaps are real, and the team works around systems instead of through them. Developing (250-399): the most common first-assessment band, where the bones are in place but tools and processes are inconsistent. Functional (400-549): the business runs without daily emergencies and most tools are used by most of the team most of the time. Strong (550-699): it runs on systems instead of heroics, with the owner no longer a daily bottleneck. Leading (700-849): a reference operation where the owner is replaceable on any given day and compliance is proactive. Optimal (850-900): the rare top band, reached by businesses where operational quality is itself the competitive moat. Most clients score between 250 and 400 on their first assessment.
The Full CTGA Assessment is a paid 7-day engagement. It produces the official Helix Score, the Helix Score Report PDF, a priority-ranked gap list across all four pillars, and an optional 30-day implementation roadmap. Before the paid assessment, the free IT Assessment Call is a 60-minute conversation with no intake form, no deck, and no pitch. On that call, the buyer walks away with the top three operational gaps named, an estimated Helix Score band, and a plain-English summary of what is broken. The 7-day timeline covers data gathering, scoring against all 40 capabilities, calibration, and report preparation. It is not a survey. The score is set by the founder of Helix Stax with the platform feeding the data, one accountable judgment rather than a software questionnaire or a committee average.
The free IT Assessment Call is always free. It is a 60-minute conversation with no intake form, no demo, and no pitch deck. The buyer walks out with the top three operational gaps named, an estimated Helix Score band, and a plain-English summary of what is broken. The Full CTGA Assessment, which produces the official Helix Score, the Helix Score Report PDF, and the priority-ranked gap analysis, is a paid 7-day engagement. We do not publish the price for paid tiers or quote in chat. The real numbers come up on the call. Beyond the assessment, the Implementation Retainer is a monthly engagement. It ends when the Helix Score reaches the agreed band threshold, not when a calendar runs out.
During an active Implementation Retainer, the Helix Score is re-scored quarterly. Quarterly cadence is meaningful at the retainer stage because gap-closing work takes time to compound: a Controls improvement made in month one typically shows in the maturity data by month three. Outside an active retainer, a reassessment is worth running any time the business changes shape significantly: a technology migration, a headcount jump, a new compliance requirement, or a leadership change. Reassessments use the same methodology version as the baseline, so scores are directly comparable. The methodology version is stamped on every Helix Score report, which is what makes before-and-after comparison defensible to investors or acquirers reviewing the business. A score without a methodology version stamp is not a CTGA score.
CMMI-derived models score per dimension on a discrete five-level ladder: Initial, Managed, Defined, Quantitatively Managed, and Optimizing. They were built for enterprise IT and Fortune 1000 transformation programs. CTGA differs in three ways. First, it produces a single Helix Score from 100 to 900 rather than a per-dimension ladder, making it comparable across quarters and defensible to investors. Second, its four pillars (Controls, Technology, Growth, Adoption) match the vocabulary an owner-operator already uses for the business, not a consultant categorizing a transformation program. Third, the score is set by the founder of Helix Stax with the platform feeding the data, one accountable judgment rather than a software questionnaire or a committee average. CTGA was built for owner-operators of 5-to-150-person service businesses, not enterprise transformation offices.
The score is a baseline, not the finished deliverable. The deliverable from a Full CTGA Assessment is the score plus a priority-ranked gap analysis: the three gaps that, closed first, move the Helix Score fastest. Most businesses do not need every gap closed at once. They need the three that pay back first. After the report, the buyer can move into an Implementation Retainer, a monthly engagement where the team closes the named gaps, trains staff on the affected systems, and re-scores quarterly. The retainer ends when the Helix Score reaches the agreed band threshold, not when a calendar runs out. Clients own all work product: documentation, configurations, automation code, runbooks, and the data behind the CTGA scores. Helix Stax retains the framework itself and the internal scoring tooling.
Yes, though we are built differently than a traditional MSP. Helix Stax delivers managed IT: helpdesk, 24/7 monitoring, device management, and security operations. The difference is the CTGA layer on top. Every client engagement includes structured maturity scoring across Controls, Technology, Growth, and Adoption. The Helix Score benchmarks where your environment sits today and tracks whether it improves over time. A traditional MSP keeps the lights on and closes tickets. We do that too, and we also tell you which systems are underperforming, what to fix first, and how to measure whether the fix actually worked. That is what the CTGA framework provides: a scored, repeatable methodology that turns IT management into a business driver instead of a recurring cost. We do not sell managed antivirus by the seat or run a break-fix operation. We take on engagements where the strategy layer matters.
What you do with the score
The score is a baseline. The deliverable from a Full CTGA Assessment is the score plus a
priority-ranked gap analysis -- the three gaps that, closed first, move the Helix Score
fastest. Most businesses do not need every gap closed. They need the three that pay back
first.