One framework. Three verticals.
Nobody pays in data.
Chapter 3 of the GVS Framework says people live in three modes — premium, balanced, survival — and that software must meet each where it is. This page is the operating consequence of that chapter: GVS Technologies is organised into three verticals, Commercial, Economical and Social, sharing one framework, one codebase and one architecture. What changes between them is who pays, how much support is attached, and how much of the work is done for you.
What does not change: the data stays where it was created. There is no GVS server holding client or personal records in any of the three verticals. The Commercial vertical is not a better-privacy tier — it is a better-support tier.
At a glance
The same tool, offered three ways. The difference is judgement and accountability, not features withheld.
| Dimension | Commercial | Economical | Social |
|---|---|---|---|
| Who it serves | Operators, banks, government bodies, enterprise delivery organisations | MSMEs, startups, NGOs, academic institutions, independent professionals | Individuals and families — anyone at all |
| Framework mode Ch.3 | Premium · Luxury — dedicated advisory & managed service | Standard · Balanced — full-featured self-serve platform | Economy · Survival — assisted simplicity, Elder Mode |
| What is paid for | Judgement, accountability and delivery leadership | Setup, training and a defined support window only | Nothing, ever. No account, no email address |
| Where data sits | Client's own perimeter / browser — never a GVS server | User's own browser — never a GVS server | User's own device — never a GVS server |
| Support | Named contact, agreed response window, contracted remediation | Configuration help and documentation; scheduled, not on-call | Community and email best-effort. No support desk exists |
| Funds | Everything below it | Its own delivery cost | Nothing — it is funded by Commercial |
The verticals in full
Each one states plainly what it is, what it costs you, and what it cannot promise.
Commercial
Organisations with governance problems attached to real money — programmes slipping, automation stalled at L3, regulators asking where the data sits, a delivery function that cannot evidence its own performance.
- Fixed-scope, fixed-fee assessments — OSS automation maturity, AI readiness, delivery governance
- Retained advisory for programmes already in flight
- Delivery leadership — PMO setup, RAID discipline, quality gates, SLA governance
- Platform deployment inside the client's own perimeter
- Office Work as a Service — running a role, not renting a tool
- Telecommunications ✓ proven — 25 years of Tier-1 delivery across Tier-1 network vendors
- Banking & Financial Services — architecture fit, no delivered engagement yet
- Government & Public Sector — architecture fit, no delivered engagement yet
- Healthcare — architecture fit, no delivered engagement yet
- Manufacturing — architecture fit, no delivered engagement yet
- A written baseline and a ranked, costed backlog you own outright
- An accountable name against a date, not a resource pool
- Remediation terms written into the engagement before it starts
- Not staff augmentation dressed as consulting
Economical
Organisations with the same governance problems and none of the budget — a 40-person MSME, an NGO with a grant to acquit, a university department, a two-person consultancy running programmes for someone larger. They are too small for enterprise licensing and too structured for a consumer app.
- The full platform, self-serve, with no feature held back for a paid tier
- Every tool runs in the browser — no server to buy, no licence to renew
- Bring-your-own AI key: you pay the model provider directly, GVS takes no margin on it
- Paid only where a person is genuinely required — configuration, training, a scoped review
- The cost of serving one more browser-native user is close to zero, so charging for access would be charging for nothing
- Charging would require an account; an account would require a server; a server would mean holding your data
- A small organisation that outgrows this becomes a Commercial client honestly, not by being throttled into one
- No SLA, no named contact, no on-call response
- No custom development inside the free tier
- No data recovery — export your backup, that is the whole safety net
- Training and configuration are scheduled work, quoted like any other engagement
The rules that hold the boundary
Three verticals sharing one codebase is only credible if the boundaries between them are written down and cheap to check.
No cross-subsidy in data, only in money
Commercial fees fund the Social vertical. Commercial clients receive nothing derived from Social users, because nothing derived from Social users exists — no telemetry, no usage analytics, no aggregate insight product. The subsidy runs one way and it is denominated in currency only.
The free tier never degrades to sell the paid one
There is no version of this where a Social or Economical tool gets worse, slower or more limited to make a Commercial engagement look attractive. Features move down the verticals, never up and out of reach.
Paying buys accountability, not privacy
All three verticals get the same architecture: on-device storage, glass-box scoring, no GVS server holding records. What a Commercial fee buys is a named person, an agreed response window and contracted remediation. Privacy was never the upsell.
Moving between verticals is a decision, not a trap
Every tool exports its full record as one JSON file. An Economical user who outgrows self-serve becomes a Commercial client by choosing to; a Commercial client who ends an engagement leaves with everything. Nothing is held hostage by format, and there is no data of yours we could withhold even if we wanted to.
How the framework maps to the verticals
All twenty-seven chapters of the GVS Framework, and which vertical each one governs. C Commercial · E Economical · S Social.
| Chapter | Subject | Verticals | What it governs in practice |
|---|---|---|---|
| 1 | Vision, mission, ground rules | C E S | Real metrics only — applies identically whether the user pays or not |
| 2 | The holistic view | C E | Approved Input → Automated Execution → Desired Output → DONE |
| 3 | Three types of living | C E S | The source chapter — premium, balanced and survival become the three verticals |
| 4 | Manifesto & hiring workflow | C | Requirement to offer letter as one accountable pipeline |
| 5 | The lifecycle doctrine | C E S | Born, battle, sunset — every tool in every vertical carries an exit |
| 6 | Knowledge hub | C E S | Field notes published openly, not gated behind a form |
| 7 | Growth, value, standards | C | The portfolio and roadmap logic behind what gets built next |
| 8 | ATDLC | C E | The automation testing & delivery lifecycle behind every release |
| 9 | Product, service, support | C E | What GVS builds and what it declines to build |
| 10 | Dashboards, KPIs & reporting | C E | The metric taxonomy every tool reports against |
| 11 | Day-to-day operations & the IAS family | C S | Where the IAS umbrella crosses from enterprise into personal use |
| 12 | A CDO's first 90 days | C | The worked case study behind delivery-leadership engagements |
| 13 | CDO Command Center | C E | Six delivery pillars, nine executive KPIs |
| 14 | IAS Office — office work as a service | C | Running a role end to end · labelled ROADMAP, not live |
| 15 | The benchmark standard | C E S | Add, Modify, Delete, Export/Import — owed to every user in every vertical |
| 16 | GVS VMS — vendor management | C E | Six-stage sourcing pipeline, five KPIs |
| 17 | GVS Daily Task | C E | Personal task log, RAID plan and KPI dashboard |
| 18 | GVS VVQ | C E | Q-Gate, ATDLC pipeline, glass-box qualification score |
| 20 | GVS Service Hub | C E | Demand triage, delivery plan, quality gate |
| 21 | GVS Email Validator | C E S | On-device email risk scoring — an individual needs this as much as an operator |
| 23 | Setu eProcurement | C E | Tender, inspection and third-party assurance after the purchase order exists |
| 24 | Vortex Sales & Delivery | C E | The order-to-delivery record every revenue metric is taken from |
| 25 | Stock Dashboard & Task Manager | E S | The survival-mode pair — whole tools, not cut-down editions |
| 26 | The portfolio register | C E S | Every tool with an honest status, including the prototype and the one that needs a server |
| 27 | The three verticals | C E S | This page, written into the framework as doctrine |
Why this survives economically
A structure that gives most of itself away has to explain its own arithmetic, or it is a press release.
The marginal cost is near zero
Every tool runs in the user's browser. GVS operates no application server, stores no user records and pays no per-user hosting cost. One more Social user costs essentially nothing to serve, so charging for access would be charging for a cost that does not exist.
Judgement is the scarce input
What cannot be given away is a person's time and accountability. Assessments, advisory, delivery leadership and configuration are priced because they consume the one input that does not scale. That is the whole business, and it is deliberately a small one.
The AI cost sits with the user
Tools that use a model use the user's own API key. The variable cost of intelligence is paid directly to the provider at cost, with no GVS margin on top — which is also why no GVS server ever needs to see the prompt or the data in it.
What this structure cannot promise
It is not proven at scale. Very few people have heard of GVS today. The Commercial vertical funds the other two, and it is currently small. If it stays small, the pace of everything below it stays slow — that is a real constraint, not a rhetorical one.
Free is a commitment, not a guarantee of permanence. The Social tools carry no paid tier and none is planned. If GVS ever could not continue them, the honest outcome is that the tools stop being updated with everything exportable — not that they quietly acquire an account wall.
No compliance guarantee. Architecture reduces exposure; your counsel confirms your obligations. Nothing on this page is legal advice.
Sub-vertical claims are disclosed, not inflated. Telecommunications is the only industry with delivered Tier-1 engagements behind it. The others are stated as architecture fit, which is a weaker claim and is meant to read as one.
Nothing to sign to start. Nothing collected either way.
If you are an organisation with a delivery problem, the assessment is the shortest honest route in. If you are a person who needs a password kept safe, take the tool and owe us nothing.
Social
People, not organisations. A parent tracking insurance renewals. A student keeping certificates safe. A shopkeeper with passwords on a scrap of paper. An elderly relative who needs one large button and their own language, not an onboarding flow.