Loading...
Ran as Custom GenAI Competency Framework. Priced at ₹29,999.
Director-level scorecards
8 new + 6 recalibrated
Before: 0 formal definitions
Δ Leadership bench architected in 2 hours
Role architecture coverage
120+ roles · 1,400 statements
Before: Ad-hoc, drift by function
Δ Enterprise-wide taxonomy
Leadership role definition cycle
2 hours facilitated + 1 week synthesis
Before: 5–9 months via consulting
Δ Compressed by 20–40×
Consulting spend avoided
~75%+ cost avoidance
Before: ₹38L baseline quote
Δ Infrastructure shipped at fraction of consulting proposal
Hiring interview anchoring
4–6 observable competencies per role
Before: Free-form job descriptions
Δ Structured protocol across 120+ roles
IP ownership
Delivered as organisation property
Before: Licensed from vendor
Δ Moat compounds for a decade
A 1,200-person Hyderabad EdTech emerging from the 2022-2023 sector correction. Growth was no longer a function of capital deployment — it was a function of talent density and role clarity. Deepa S. took the CHRO chair with a board-signed brief to expand the leadership bench from six directors to fourteen inside six weeks. Eight new director-level seats budgeted at ₹80L–₹1.5Cr bands — Engineering, Product, Content, Sales, Customer Success, Marketing, Finance, Operations. None of them had been defined. Three consulting firms had pitched — ₹38L to ₹62L, 5–9 months. All three sold documents. Deepa wanted infrastructure. She named the distinction in her first meeting with Priya and it has been quoted inside the EdTech's people-ops team every quarter since: Consultants sell PDFs. Operators install engines. PDFs gather digital dust. Engines generate ROI forever. That single phrase defined what got built.
Custom Competency & Skills Architecture engagement delivered in 8 weeks. Phase 1 (Weeks 1–2) — calibration of Priya's 3,000+ statement library against the EdTech's two-year product roadmap, revenue-mix shift, and cultural non-negotiables, producing a 1,400-statement subset delivered as organisation IP (not licensed). Phase 2 (Week 3) — the two-hour leadership mapping session that became internal folklore. Nine people in a conference room — CEO, President, CHRO, six business heads. Priya facilitated every role through the Four-Question Leadership Role Protocol: 18-month outcome ownership, non-negotiable competencies, 90-day dealbreakers, observable good-versus-great differentiators. Fifteen minutes per role. Eight roles. Two hours. No overruns. CEO's closing line has been quoted every quarter since: 'We've been trying to do this for fourteen months. We just did it in two hours.' Phase 3 (Weeks 4–8) — full organisation rollout. 120+ role scorecards. 3,000+ statement coverage. Four leadership tracks with IC-to-Director progression. Hiring scorecards regenerated. Performance reviews restructured (annual ratings replaced with quarterly competency conversations). System live Week 9 — one week ahead of commitment.
PDFs gather digital dust. Engines generate ROI forever.
A PDF is a document. It lives in a Notion page, a printed binder, a SharePoint folder. It is referenced episodically — during annual performance cycles, during promotion reviews, during onboarding. It is owned by HR. It is updated every two to three years when someone remembers. It generates a one-time invoice. Then it gathers digital dust. An engine is what the business runs on. It is the shared language hiring managers use to interview every Monday morning. It is the scorecard performance reviews are anchored to every quarter. It is evolved continuously, not revised periodically. It compounds every quarter the business operates. It generates ROI forever. This is why the ₹38–62 lakh consulting quotes were the wrong deal — not because they were expensive, but because they were PDFs dressed up in calendar months. Consultants sell PDFs because PDFs are billable. Operators install engines because engines are what the business actually uses on Monday morning.
Consultants sell PDFs. Operators install engines. PDFs gather digital dust. Engines generate ROI forever. We stopped buying PDFs from consultants in 2024 and started building our first talent engine. It is the best talent-architecture decision this company has ever made. Priya did not give us a deliverable. She installed an engine the business runs on every Monday morning, five years out.— Deepa S., CHRO, Indian EdTech (1,200+ employees, Hyderabad)
Every downstream engagement decision — library sourcing, facilitation design, rollout sequencing, IP ownership, enablement depth — follows from whether the CHRO is buying a PDF or installing an engine. PDFs are billable in calendar months. Engines compound every quarter the business operates. A consulting PDF that costs ₹40 lakhs and depreciates to zero in eighteen months is an expense line with a bad unit economic profile. An operator-installed engine that costs a fraction of that and compounds for a decade is capital expenditure on a moat. If the proposed deliverable is a document, the deal is wrong.
The fastest way to burn the first two months of any competency engagement is to start with a blank page. A well-engineered library of 3,000+ statements refined across enterprise accounts already exists. Week-One work is calibrating that library to the specific operating context of the business — which statements apply, which language fits the culture, which proficiency levels match the maturity of the organisation. Construction-from-zero is vanity. Calibration is velocity.
Every consulting proposal sequences leadership role mapping as the endpoint of a six-to-nine-month engagement. That sequencing is wrong. Leadership roles are the highest-stakes, highest-urgency talent decisions any organisation faces, and they typically come with a hiring clock attached. The leadership mapping should happen in Week Three — once the library is calibrated. Reverse the consulting sequence and the engagement compresses from nine months to eight weeks.
The reason the two-hour session worked was not facilitation skill. It was Week-One and Week-Two engineering — the calibrated library on every seat, the Four-Question Leadership Role Protocol, the fifteen-minute-per-role time box, the pre-selected cohort of nine decision-makers in the room. When the session started, the group was selecting from a known menu under a structured protocol. Sessions that try to discover the framework live are the ones that end without deliverables.
A competency library that reverts to the vendor at the end of the engagement is a rental agreement. For a business expected to scale its headcount materially over the next 24–36 months, rental is the wrong structure. The framework must be delivered as the organisation's property — with the right to extend, modify, retire, and evolve without vendor permission. If the IP reverts, the competitive moat evaporates with it.
“Consultants sell PDFs. Operators install engines. PDFs gather digital dust. Engines generate ROI forever. The difference between a generic competency framework and a competitive talent moat is the facilitation — the discipline of mapping eight leadership roles in a single two-hour session while the CEO, the President, and the business heads are in the room together.”
Post-correction fundraising scrutiny, global investor focus on unit economics, and the rising cost of director-level mis-hires have combined to make talent architecture a board-level concern for the first time. Consultants sell PDFs. Operators install engines. The CHROs commissioning engines in 2026 are the ones building talent infrastructure that compounds into valuation. The ones still commissioning PDFs are the ones explaining to boards, in 2028, why their leadership bench underperformed and why their framework stalled inside the first performance cycle. The distinction is not semantic. It is the difference between a line item that depreciates and an asset that compounds.
A PDF is episodic — referenced during annual reviews, then ignored. An engine is continuous — hiring managers, performance reviewers, and succession planners all speak the same language Monday to Monday. When you evaluate a competency-framework proposal, ask: 'Which surfaces of the business will be running on this six months after handover?' If the answer is 'annual performance cycle,' you are buying a PDF. If the answer is 'every hiring panel, every quarterly review, every career conversation, every succession discussion,' you are commissioning an engine.
The two hours only work because the two weeks before them are engineered correctly. A 3,000+ statement competency library is calibrated to the organisation's operating context in Week 1. The Four-Question Leadership Role Protocol is pre-structured to force scarcity (max 7 competencies, max 3 dealbreakers). The right nine decision-makers are in the room. With those preconditions, each role takes fifteen minutes of structured conversation. Consulting firms take five to nine months because their sequencing is inverted — they treat leadership mapping as the endpoint of a long diagnostic rather than the opening act after calibration.
Consulting firms bill calendar months. The engine delivers value every Monday morning for the next decade. The unit economics are inverted — a ₹40L PDF that depreciates to zero in eighteen months is an expense line with a bad unit economic profile. An operator-installed engine that costs a fraction of that and compounds for a decade is capital expenditure on a moat. Priya prices the engagement at what the installation costs, not what the calendar months cost.
Yes. The competency library, the role scorecards, the hiring interview guides, the performance review scaffolding, and the career path architecture are all delivered as the organisation's property with a signed IP-transfer clause. No reversion. No renewal dependency. The engine is the organisation's for as long as it chooses to operate.
This current package is separately scoped from the historical project for Indian EdTech (Hyderabad) — 1,200+ employees. A framework package covers one role family; broader multi-role or multi-month work needs an agreed scope. Review the service, then arrange a scoping call.
Skills Architecture Starter
On Kreativish
PlaybookComplete Guide to Competency Frameworks
On Kreativish
Playbook50 Ready-to-Use Competency Statements (Tech Roles)
On Kreativish
PlaybookPlug and Play Competencies: Next-Gen Tech Roles
On Kreativish
PlaybookSkills Taxonomy Design
On Kreativish
InfrastructureCompetency Framework Builder XLSX
On Kreativish
InfrastructureSkills Taxonomy Design XLSX
On Kreativish
BFSI
Kotak Mahindra Bank
Annual attrition (high-turnover branch roles): 45% → 28%
Manufacturing
Yamaha Motor India
New-hire ramp time: 8 weeks → 5.6 weeks
InsurTech
Indian InsurTech (Hyderabad) — 800+ employees
AI tools in production (L&D-owned): 0 → 3 live tools
FinTech infrastructure
Perfios Software Solutions
Enterprise upsell revenue (attributed): - → ₹45L across 6 accounts
BFSI L&D · Individual Contributor
Senior Instructional Designer · Top-5 Indian Private Bank
Role progression: Senior Instructional Designer (3 years stagnant) → L&D Lead (8 direct reports)
EdTech L&D · Individual Contributor
L&D Manager · Bangalore Mid-Market EdTech
Role title: L&D Manager → AI Learning Architect (role created around his portfolio)
SaaS Scale-Up · One-Person L&D
Solo L&D Practitioner · Hyderabad Scale-Up (400 employees)
Weekly hours freed: 62-hour work weeks (burnout zone) → ~22 hours/week freed for strategic work
B2B SaaS · L&D Team
L&D Team · Gurugram B2B SaaS (150 employees)
AI tools deployed (team-owned): 2-3 ad-hoc individual experiments → 17-tool production AI stack with domain ownership
B2B SaaS · HRBP + L&D Team
HRBP Team · Pune Series C B2B SaaS (300 employees)
Role scorecards mapped: 0 formal scorecards (free-form JDs) → 40 roles (32 new + 8 recalibrated)
BFSI Back-Office · HR+L&D Team
HR+L&D Team · Mumbai BFSI Back-Office (600 employees)
Regulatory deadlines met: 3 converging deadlines · no existing infrastructure → All 3 shipped inside the 10-week window
