Operating thesis
Turn scattered work into reusable leverage.
The first 100 days are about listening, mapping, and converting recurring work into a clear operating system for the founders, the consultants, and the content engine behind Amaranth.
Founders Associate interview prep
The first 100 days should create leverage, not noise.
This page is the editorial shell for the final 100-day plan and the longer 300-day outlook. It is structured so the final copy from the personal-hq prep folder can drop in without changing the layout.
100
days to build leverage
3
phases in the operating plan
300
days of strategic outlook
1
shared source of truth
The visual language is intentionally consulting-like: editorial rhythm, disciplined spacing, restrained motion, and a layout that reads more like a strategic memo than a marketing page.
100-day plan
The primary narrative stays centered on the first 100 days.
This section is the core deliverable. It should feel complete on its own, with enough structure to absorb final copy without any layout changes.
200-300 day outlook
The page also shows where the work evolves next.
The outlook is intentionally secondary. It shows how the operating model, content cadence, and AI layer can mature beyond the initial 100-day burst.
Operating thesis
Turn scattered work into reusable leverage.
The first 100 days focus on understanding how the boutique really works, where the recurring friction sits, and which activities can be turned into systems, templates, and assets that save time across the team.
The page is intentionally structured around the logic already established in the final plan: listen first, standardize next, then own a visible wedge and build the foundation for the next quarter.
100-day plan
Three phases, one operating arc.
Days 0-30
Listen, map, and earn trust
Understand the actual operating reality before changing it. The goal is to reduce friction, capture the informal structure, and surface a practical quick-win backlog.
Key moves
- Run structured listening sessions with the founders, Heike, senior experts, and active consultants.
- Build a living operating map across customers, projects, pipeline, content, tools, and decision ownership.
- Identify 10-20 small frictions and ship 3-5 quick wins that create immediate relief.
- Audit the existing whitepapers so the strongest assets can be upgraded in phase two.
Expected outputs
- Listening report with the core bottlenecks and hidden leverage points
- Operating map as a living document
- Quick-win backlog with 3-5 completed fixes
- Proposal for a stable weekly operating rhythm
Days 31-60
Standardize the repeatable work
Convert the most common delivery, content, and BD tasks into reusable formats so the team stops rebuilding the same assets repeatedly.
Key moves
- Upgrade the strongest whitepapers into web-plus-PDF packages with better structure, readability, and cross-linking.
- Create a media / thought-leadership surface for audio and video content that already exists.
- Build modular BD assets for the highest-value themes and engagements.
- Prototype a small AI workflow layer for research briefs and post-meeting synthesis.
Expected outputs
- Three upgraded whitepaper packages
- A visible media hub or content module
- Reusable pitch modules for core themes
- A lightweight knowledge-base taxonomy
Days 61-100
Own a wedge and systematize growth
Move from support into ownership: one visible workstream, one repeatable content rhythm, and a simple metrics layer that can guide the next quarter.
Key moves
- Take ownership of one GTM wedge with research, story, pitch materials, and target-account logic.
- Publish a recurring regulatory radar or similar recurring insight format.
- Turn the strongest projects into anonymized case studies.
- Prepare the first invite-only roundtable and a clean 100-day readout.
Expected outputs
- A complete GTM package for one wedge
- At least two recurring insight outputs
- Two to three anonymized case studies
- A metrics view with a documented baseline
Working model
Founder leverage
Anything that removes repeat translation work from the founders belongs here: operating rhythm, decision logs, meeting synthesis, and the first layer of structured support.
Working model
Revenue leverage
The BD layer becomes sharper when research, pitch framing, content, and follow-through are packaged into reusable modules rather than one-off effort.
Working model
Delivery leverage
Delivery gets lighter when recurring templates, content structures, and simple knowledge retrieval reduce the time spent recreating fundamentals.
Content system
The page is ready for final copy, not a redesign.
Chatbot space reserved
A future chatbot can sit in this area without changing the page structure. The intent is to add an Amaranth-specific layer later, once the core page content and the interview story are stable.
Integration note
Keep the embed decoupled from the shell so the layout can stay intact whether the chatbot is live, paused, or replaced later.
200-300 day outlook
What the 100-day plan can evolve into.
Trajectory
Operating maturity
More explicit responsibilities, less person-dependent delivery, and a smoother onboarding path for new operators and consultants.
This is the most likely next step if the first 100 days work.
Trajectory
AI and systems layer
A safe, bounded internal AI layer for research, briefing, and proposal workflows that reduces repetitive work without diluting judgment.
AI stays a productivity layer, not a consulting replacement.
Trajectory
Growth and capacity
A recurring content rhythm, invite-only events, productized assets, and the operational basis for a small internal operator team if needed.
This becomes the basis for the next operating step after 300 days.
Risks
What could break the plan.
Building too early
The main risk is to formalize tools or platforms before the real workflows are understood. The plan avoids that by starting with listening and mapping.
Low signal assets
If whitepapers, case studies, and pitch materials are not consistently packaged, the external signal stays weaker than the actual expertise.
Operator overload
The role only works if it actually reduces founder and delivery load. Otherwise it becomes another coordination layer instead of leverage.
Dependencies
What the build depends on.
- Access to founders, Heike, and a small sample of active consultants
- The existing Amaranth whitepapers, audio/video assets, and pitch materials
- A clear editorial decision on which wedge to emphasize first
- A lightweight channel for ongoing source updates from personal-hq
Closing note
Built now, finalized later.
The shell is ready for final copy, richer proof points, and a later Amaranth-specific chatbot. The structure should not need to move when the content gets sharper.
Source note: Canonical content source: F:\Github Repos\personal-hq\active\interview-prep\amaranth-advisory\100-day-plan-final.md