Kenny Damian@Kenny_GTM
How to Build a Services-as-Software Delivery Stack
Kenny Damian's six systems for scaling client delivery
- post
- Saved
Written by AI
- TLDR
- Kenny Damian details 6 systems that keep AI delivery costs flat as Frontal scales from 2 to 275 client accounts.
- Best for
- Agencies and service businesses doing AI work for 2 or more clients.
- The tip
- Give each client its own folder and a context.md with their ICP, offer, personas, what works and what doesn't. Decide which source wins when they disagree, before an agent runs.
- Time
- About 5 minutes to connect each tool. He doesn't give a total.
- What you need
- Claude Code
- your own API keys for each client
- The prompt
check for exposed API keys and vulnerabilities
- Start here
- One folder per client, own keys.
- CLAUDE.md at the root, under 200 lines.
- context.md per client, sources ranked.
postThe source
Kenny Damian@Kenny_GTMMedia saved
- Highlights
You price a result instead of hours, you say software does the work, the client signs.
At Frontal we have done this work across 275 companies and the same thing is true every time: companies buy the tools and cannot make them run.
I open-sourced the 15 skills we run across 70+ clients. 5 pillars, roughly 4,200 lines of methodology.
Across the agency that store now holds 11,000 campaigns, 132,000 snapshots and 30+ clients.
- Excerpt
I have 15 client folders open in my terminal right now. Opening the 15th cost me about what the 2nd did, and that single fact is the whole difference between a services-as-software company and an agency paying for a Claude subscription.
From x.com