Services · Flagship Offering
Citizen Development
Every employee, now an AI developer.
The technology is finally ready. Claude — combined with Projects, Skills, Model Context Protocol, and Claude Code — means any employee who can describe their work can now build applications, automate workflows, and query live operational data against real systems. Without a software engineering background.
Your team is already building. Someone automated a workflow on her laptop that saves three hours a week. A sales coordinator built a tool nobody else can use. None of it is governed. None of it scales. Citizen Development installs the infrastructure that changes that — and connects it to your live operational data.
Week 3
Most clients have something running by production.
2 to 12 weeks
Depending on scope and team size
Flagship
Our most-delivered, highest-return offering
What the first 30 days look like
Week 1
Discovery and design — we talk to the people doing the actual work, find out what they have already built, and design the SDLC plugin and guardrails architecture around what we find. Not a template.
Week 2
Build and configure — we build the custom SDLC plugin with four to five purpose-built skills, configure the guardrails scaffolding, and connect the governed data layer through MCP.
Week 3
Deploy and enable — the plugin goes live in your Claude Teams environment. We run the hands-on enablement workshop. Every participant builds something on their own laptop. Recorded for future team members.
Day 30 — what you have
A governed Claude environment deployed across your team. Every authorized employee working from the same standardized starting point. Live data connectivity through MCP. A graduation path for moving proven applications into production. Your team actually using it.
What we deliver
Workflow and capability discovery
Direct conversations with the people doing the real work — finding what each person owns, what they have already built, and where the highest-value automation opportunities are.
Custom SDLC plugin
Four to five purpose-built Claude skills standardizing how any employee begins a new project. Published once to your Claude Teams environment, available to every authorized user.
Enablement workshop
Hands-on session — every participant builds something on their own laptop. Not a slide presentation about AI potential. Recorded for future team members and onboarding.
Context engineering templates
CLAUDE.md files, project-level context structure patterns, and proven approaches to instructing Claude effectively. Every citizen developer builds on a shared foundation.
Guardrails scaffolding
Branch protection, required review on Claude-generated pull requests, per-project sandbox environments, and least-privilege data access. Built before anyone starts building.
Governed data connectivity via MCP
Your team builds against real operational data, not exports. Custom MCP servers with governed access, role-based permissions, and full audit logging.
Graduation playbook
A documented path for moving a proven citizen developer application from the R&D stack into full production on GCR, AWS, or Azure.
Hypercare support
Dedicated channel, weekly sync calls, prompt bug resolution, and skills iteration based on observed usage. We stay on until it’s running reliably.
Right for you if
- Your team is already using Claude informally and you need governance before the sprawl becomes a liability
- You want every employee operating at the level of your best AI user — not just the ones who figured it out themselves
- You want to multiply workforce output without waiting six months for a top-down deployment
- You are ready to connect your team’s AI capability to live operational data through MCP
Not right for you if
- Your organization has fewer than five people who could realistically use a Claude-based development environment
- Your data environment has not been stabilized — we will find the gaps in week one, and the engagement requires addressing them
- You are looking for a pilot with no defined governance or production path — we do not deliver proofs of concept that are not designed to ship
Frequently Asked Questions
Timeline
3 to 12 weeks from kickoff depending on delivery tier