On this page13
- What did a traditional PR account team actually do?
- The 1 + 1 + Stack model
- How many hours does each role need per week?
- What should the weekly handoffs look like?
- Which AI tools belong in the stack, and what checks do they need?
- Why is a fractional senior operator often the right first hire?
- When does this structure break?
- How do you grow the team when it outgrows this setup?
- FAQ
- Can one person really replace an agency account team?
- Who should be the internal owner if we have no marketing hire?
- Should the senior operator be in our time zone?
- Is this structure different for Web3 and AI companies?
The simplest small PR team structure in 2026 has three parts: one senior operator who owns strategy and media relationships (often fractional), one internal owner who gets answers and approvals fast, and a set of AI tools that handle the production work an account team used to do. Each part has clear hours and clear handoffs. That setup covers most of what a seed to Series A startup needs from PR, at a fraction of the coordination cost of a traditional agency team.
It isn't the right structure for everyone, and I'll be specific about where it breaks.
What did a traditional PR account team actually do?
To design a smaller team, it helps to know what the bigger one was for. A classic agency account usually had a senior lead who appeared at the kickoff and in monthly reviews, a manager who ran the plan day to day, and one or two junior staff doing the volume work.
Most of the hours sat at the bottom of that pyramid:
- Building and updating media lists
- Researching reporters and recent coverage
- First drafts of releases, pitches and briefing notes
- Formatting pitch variations per outlet
- Daily monitoring and coverage clipping
- Monthly reports
That's the work AI now drafts well. The senior judgment at the top of the pyramid, the part a founder actually wanted, was often the thinnest slice of the retainer. I worked at Web3 agencies early in my career, and I wrote about the capacity problem a few years later:
Funded web3 projects run behind mainstream PR agencies so that they can get substantial coverages But what they don’t realise is that these PR agencies are at max capacity with clients & already diluting the attention of their journalists. Shilika Jain on X, 16 Dec 2022
The new structure flips the pyramid. Senior time becomes the largest share, and the volume work shrinks because tools draft it and the senior person checks it.
The 1 + 1 + Stack model
I call this the 1 + 1 + Stack. One senior operator, one internal owner, and a tool stack. The roles split like this.
| Role | Who it is | Owns | Does not own |
|---|---|---|---|
| Senior operator | Fractional head of PR or an experienced in-house lead | Narrative, story selection, reporter relationships, pitching, interview prep, crisis calls, final review of everything | Internal approvals, chasing engineers for facts |
| Internal owner | Founder, CMO, or a marketing generalist inside the company | Fast answers, approvals, access to product and data, spokesperson availability | Media strategy, reporter contact |
| Tool stack | AI drafting, research and monitoring tools | First drafts, list building, monitoring summaries, repurposing, report formatting | Any decision, any final copy, any direct reporter contact |
The internal owner is the role most teams skip, and it's the one that decides whether this works. A senior operator outside the company is only as fast as the person inside who can confirm a number, book the founder for an interview or approve a quote.
How many hours does each role need per week?
These are illustrative ranges for a startup running steady PR with one or two announcements a quarter, not a quote. Busy weeks around a launch or funding round will run higher.
| Role | Steady weeks | Launch weeks | What fills the time |
|---|---|---|---|
| Senior operator | 8 to 15 hours | 20+ hours | Pitching, reporter follow-ups, prep calls, editing AI drafts |
| Internal owner | 2 to 4 hours | 6 to 10 hours | Weekly sync, approvals, collecting facts and data |
| Founder as spokesperson | 1 to 3 hours | 4 to 8 hours | Interviews, podcast recordings, reviewing op-ed drafts |
| Tool stack | Runs continuously | Runs continuously | Monitoring, drafting, summarising |
The founder row matters because founder time is the scarcest input in startup PR. AI can draft a bylined op-ed from a recorded conversation, which saves the founder hours of writing. It can't sit the interview for them.
What should the weekly handoffs look like?
A small team lives or dies on handoffs. Without an account manager chasing everyone, the rhythm has to be explicit. This is the weekly loop I'd set up:
- Monday: sync (30 minutes). Senior operator and internal owner review what's coming: product news, data, events, founder availability. Decide this week's one or two story priorities.
- Monday to Tuesday: research and drafts. Tools pull reporter coverage and draft pitch variants. The senior operator selects targets and rewrites pitches in their own voice.
- Tuesday to Wednesday: approvals. Internal owner confirms facts and gets sign-offs within 24 hours. Anything slower pushes pitching to the following week.
- Wednesday to Thursday: outreach. Senior operator pitches and handles replies personally. Follow up once after three to four working days.
- Friday: summary. Tools compile coverage and monitoring into a short note. Senior operator adds two lines of interpretation: what worked, what to change.
The 24-hour approval rule is where most small teams fail. I've seen it at much bigger organisations too:
the more I collaborate with these ecosystems, I feel that their comms suck whereas it should be the other way round delayed responses, lack of collaboration, missing deadlines, being too picky w journos lol Shilika Jain on X, 10 Nov 2025
A big comms team with slow approvals loses to a small one that answers reporters the same day. Structure is less about headcount than response time.
Which AI tools belong in the stack, and what checks do they need?
I won't recommend specific products here because they change monthly. Think in categories instead:
- Drafting: first versions of pitches, releases, briefing notes, social posts.
- Research: summarising a reporter's recent articles, pulling competitor coverage, background on a trend.
- Monitoring: brand and keyword mentions across news and social, with summaries.
- Repurposing: turning one interview or op-ed into posts, threads and newsletter snippets.
- Reporting: formatting coverage lists and metrics into a monthly view.
Every output gets one human check before it's used: facts against a source, names spelled right, claims defensible. No tool sends anything to a reporter directly. A pitch that reads as generated damages the senior operator's relationships, which are the most valuable thing in the whole structure. For a fuller list of tools by category, see my AI marketing tool stack for startups.
Why is a fractional senior operator often the right first hire?
Because the senior judgment is the part you can't automate, and early-stage companies rarely need it 40 hours a week. A fractional lead gives you that judgment and existing reporter relationships for the hours you actually use. I've written about the trade-offs in detail in fractional head of PR vs agency vs in-house, and how an engagement runs in practice in fractional PR for AI startups.
What a founder should not do is skip the senior role and run PR alone with AI tools. The mistake is old, the tools just make it look easier:
one of the stupidest things early stage founders do is trying to do everything on their own. Shilika Jain on X, 29 Oct 2022
AI lets a founder produce a lot of PR material. It doesn't give them the relationships or the outside view to know which story will run and which will be ignored.
If you want the senior operator seat covered, that's the role I play in my AI startup PR and Web3 PR campaign work.
When does this structure break?
Be honest about the limits before you commit to it.
- Single point of failure. One senior operator means one person's availability. If they're sick or travelling during a crisis, you need a named backup.
- Multi-market launches. If you're announcing in Korea, Japan and Vietnam the same week, one operator can coordinate it, but you'll need native-language partners for outreach and review. AI translation is a draft, not a release.
- Sustained crises. A serious incident can need someone on it 12 hours a day for a week. That's beyond a fractional allocation unless you've agreed surge hours in advance.
- Heavy event calendars. On-ground media support at several conferences a quarter needs extra hands.
- Late-stage companies. Once you have multiple product lines, regulators, investor relations and internal comms, you need a proper in-house team. The 1 + 1 + Stack is a starting structure, not an end state.
How do you grow the team when it outgrows this setup?
Add people in the order that relieves the real bottleneck, not the order an org chart suggests:
| Signal | Next hire |
|---|---|
| Internal owner can't keep up with approvals and content | A content or comms coordinator in-house |
| Senior operator is over hours every month | Increase the fractional scope, or hire an in-house lead with the fractional person as advisor |
| Regional coverage becomes a priority | Regional PR partners per market |
| Founder demand for interviews exceeds availability | A second spokesperson, trained for media |
Each step keeps the same principle: senior judgment on strategy and relationships, people close to the product for speed, and tools for volume.
FAQ
Can one person really replace an agency account team?
For a seed to Series A startup with a focused narrative, often yes, because AI covers much of the volume work the junior layer used to do. What one person can't replace is breadth: many markets at once, round-the-clock crisis coverage or a packed event calendar. Size the team to the plan, not to the headcount an agency would quote.
Who should be the internal owner if we have no marketing hire?
Usually the founder or a co-founder who is close to product and can approve facts quickly. It's a few hours a week, not a full role. The key is that one named person answers within a day, so the senior operator isn't waiting.
Should the senior operator be in our time zone?
Ideally they overlap with yours for a few hours a day and with the reporters you're targeting. For APAC launches, an operator in Asia can be an advantage. What matters most is response time when a reporter asks a question.
Is this structure different for Web3 and AI companies?
The roles are the same. Web3 teams usually add community channels and KOL coordination to the stack, and AI companies tend to need more technical review of claims. In both cases, the senior operator should know the sector's reporters, not just PR in general.
Figuring out who should run PR at your startup? Book 30 minutes and we'll map the team together.
