The way humans use software has changed forever.
Claude Code is now our most used interface.
We uniquely blend software and human expertise.
We call it โAI-Native Servicesโ.
Hereโs how it works operationally:
1๏ธโฃ Company OS in git
Our entire company dataset lives in one GitHub repo called Company OS.
What's inside:
- company/ - team, voice guide, design system, industry intel
- wiki/ - SOPs, playbooks, campaign guides
- clients/ - per-client context files
- raw/ - client calls, market research, competitor data
- plugin/ - 26 agents, 23 commands, hooks
- skills/ - 79 Claude skills
Data is constantly flowing in to keep it up-to-date.
2๏ธโฃ Client repos
Every client gets their own private repo.
Same engineering pattern as the Company OS, just personalized to their account.
What's inside:
- Their ICP, voice guide, brand assets
- Historical campaigns and what worked
- Onboarding form data and deep research
- Slack threads, call transcripts, GDrive changes
- API/MCP connections to their revenue stack
Result: every team member has full client + company in every session.
3๏ธโฃ Human interaction layer
We still log into some SaaS UIs, but Claude is slowly taking over.
Across 20 team members, the efficiency gain has been massive.
We try to automate as much of the admin as possible:
- Client onboarding
- Content research and ideation
- Skill tuning from team feedback
- Reply triage + sentiment routing
- Campaign launch pre-flight checks
So AI does the legwork, but humans ship.
So we can spend more time on strategy + creative GTM.
4๏ธโฃ MCP + CLI engine
MCPs + CLIs let Claude act across our stack vs. just advise.
Some of our favorite MCPs/CLIs:
- GitHub - Company OS + client repos
- Findymail - email verification waterfall
- Google Workspace - client docs
- Airtable - automation backend
- Instantly.ai - email campaigns
- Slack - team + client comms
- Apollo.io - list + enrichment
- Notion - internal wiki + PJM
- HeyReach - DM sequences
Plus HubSpot, Browserbase, Supabase, Vercel, Figma, Stripe, Pinecone, Clay, Apify, Firecrawl, and more.
We're also migrating a ton of workflows to custom code.
5๏ธโฃ Operationalize
As an AI-native services company, we're constantly optimizing how we work with AI and software.
Built into the system:
- Guardrails: safety hooks gate 94+ risky operations.
- PR-based governance: anyone on the team can propose a new skill, agent, or tweak as a branch.
- Workflows-engineering plugin: 26 agents, 79 skills, 23 commands auto-propagated. Agent swarms split tasks into 5-20 sub-agents.
- Self-improvement loop: n8n syncs tech stack data back into the Company OS. Pinecone stores past content + performance metrics for skills to query. Human corrections feed back in.
There isn't ever going to be a finish line, so we're building like it's a marathon.
---
The way Workflows.io operates wouldnโt be possible 1 year ago.
But we predicted this and made a big bet on AI-Native Services.