Chapter 01
One briefing. Every morning. Before you open a single app.
PersonalOS is a bespoke operating system for founders — built in-house, running live. It pulls from nine sources across calendar, tasks, communications, and industry news, synthesises everything with the Claude API, and delivers a prioritised daily briefing via WhatsApp and a live dashboard. A chat interface lets you interrogate any detail on demand.
Built by Ammodus. Used by Ammodus.
This is not a concept — it's running daily
PersonalOS was built to solve a real problem inside our own business. We use it every day. It's available as a bespoke build for other founders — configured to your tools, your voice, and your priorities. Every deployment is custom.
What it produces every morning
9
Live integrations
All synthesised into one briefing
1hr
Saved daily
Context-switching eliminated before 9am
07:30
WhatsApp briefing lands
Before the working day begins
100%
Days started with full context
No more reactive mornings
How it was built
1
Week 1–2
Design
Map the inputs
Audited every tool and source that needed daily attention — calendar, tasks, communications, news. Defined exactly what the briefing should surface and in what order of priority.
2
Week 3–5
Build
Build the pipeline
Custom code built to pull from each integration, normalise the data, and pass it to the Claude API with a structured prompt. Dashboard built to display all sources live. WhatsApp delivery configured via Twilio.
3
Week 6+
Refine
Tune the intelligence
The briefing prompt was refined over six weeks — adjusting what gets flagged as urgent, how risks are surfaced, and how the AI digest formats news relevance. Now runs without intervention.
Chapter 02
Nine integrations. One briefing. Zero tab-switching.
PersonalOS connects to every tool that matters in a founder's day — then does the work of reading, synthesising, and prioritising across all of them so you don't have to.
Live integrations
Google Calendar
Schedule layer
Today's events, upcoming deadlines, prep time flagged before important meetings.
Real-time
Notion
Tasks & projects
Open tasks, overdue items, and project status pulled and prioritised by urgency.
Synced nightly
Gmail
Email digest
Unread emails summarised. Action-required threads flagged. Nothing buried.
Morning pull
Slack
Team comms
Unread mentions, blocked tasks, and team updates surfaced. No scrolling required.
Real-time
Linear
Dev & build tracking
Open issues, sprint status, and anything marked urgent pulled into the daily view.
Synced daily
Spotify
Focus state signal
Now playing displayed on the dashboard. Morning playlist suggested based on the day's schedule intensity.
Live
News API
Industry intelligence
AI-filtered news digest. Only articles relevant to AI, automation, and the founder's specific vertical. Noise filtered out.
Daily digest
X / Twitter
Signal & trend pulse
Top posts from followed accounts in the AI/automation space summarised. No doomscrolling required.
Morning pull
WhatsApp
Briefing delivery
The full briefing delivered as a formatted WhatsApp message at 07:30 every morning via Twilio. Read it before you get out of bed.
07:30 daily
What the morning briefing looks like
Morning briefing — example output
Anonymised · Real format
WhatsApp — delivered 07:30
PersonalOS · Chief of Staff
Dashboard — live panels
Today's calendar
Client call — A10:00
Client call — B14:00
Free window15:00–18:00
Open tasks
Proposal — client BDue Fri
Review onboarding docToday
Send invoice — ADone
Team status
Website buildIn progress
Case study draftOverdue
Client C setupOn track
Inbox signals
Unread emails14
Action required3
Slack mentions7
The AI digest — industry intelligence
AI & automation digest
Generated daily · filtered for relevance
OpenAI
GPT-5 launches with extended context and improved tool use
Relevant to your current client stack — particularly the document processing workflow you're scoping for client C. Worth evaluating as a drop-in upgrade.
TechCrunch
UK SMEs accelerating AI adoption — KPMG survey, 2026
Survey data showing 61% of UK SMEs plan to increase AI spend this year. Directly usable as positioning material in your professional services outreach.
X / Twitter
Make.com vs n8n debate resurfaces — thread by @levelsio gaining traction
Useful context for your tool positioning conversations. The thread surfaces several objections your prospects may raise — worth scanning before client calls.
Chapter 03
The problem: building a business across nine tools is a full-time job in itself.
For a founder running multiple client engagements, a growing team, and their own pipeline — the overhead of staying on top of everything was consuming the first hour of every day before any real work began.
What the mornings used to look like
The daily tax
Every morning started the same way. Open Slack — scroll through overnight messages. Switch to Gmail — triage inbox. Open Notion — try to remember where everything was. Check the calendar — realise there's a call in 20 minutes that hasn't been prepped for.
By the time context had been gathered across all the tools, 45–60 minutes had passed. The day was already reactive before it had started.
The bigger problem: things were being missed. A team task that had gone overdue. An email that needed a same-day response. A piece of industry news that would have been useful in a client call two days ago.
By the time context had been gathered across all the tools, 45–60 minutes had passed. The day was already reactive before it had started.
The bigger problem: things were being missed. A team task that had gone overdue. An email that needed a same-day response. A piece of industry news that would have been useful in a client call two days ago.
Why tools alone don't fix it
The problem wasn't the tools — Notion, Gmail, and Slack are good products. The problem was the cognitive overhead of stitching them together manually every morning.
Notification aggregators were tried. Dashboard tools were tried. None of them synthesised across sources or told you what actually mattered that day — they just centralised the noise.
What was needed wasn't a better inbox. It was an intelligent layer on top of all the inboxes — something that could read across everything, apply judgment, and surface what needed attention in priority order.
Notification aggregators were tried. Dashboard tools were tried. None of them synthesised across sources or told you what actually mattered that day — they just centralised the noise.
What was needed wasn't a better inbox. It was an intelligent layer on top of all the inboxes — something that could read across everything, apply judgment, and surface what needed attention in priority order.
The cost of a scattered morning
55min
Average morning context-switch time
Before first focused work block
9
Tools checked every morning
Each requiring active attention
3–4×
Weekly reactive days
Spent responding rather than building
0
Proactive daily prioritisation
No system to surface what actually mattered
Chapter 04
The solution: a chief of staff that reads everything so you don't have to.
PersonalOS is built on a simple principle — all the reading, filtering, and prioritisation should happen before you touch a single app. By the time you engage with any tool, you already know what matters and why.
Three layers of intelligence
Operational layer
Calendar, tasks, team, comms
Pulls from Google Calendar, Notion, Linear, Gmail, and Slack. Identifies overdue tasks, approaching deadlines, blocked team members, and emails requiring a response — ranked by urgency. The briefing tells you what needs to happen today, not just what's on the list.
Intelligence layer
News, X, industry signals
Pulls from the News API and X, filters for AI, automation, and vertical-specific content, and summarises each item with a relevance note — explaining why it matters to your current clients or pipeline. No raw feeds, no noise, no doomscrolling.
Chat layer
On-demand chief of staff
The dashboard includes a live chat interface powered by the Claude API, with full context of the day's briefing loaded in. Ask it anything — "what's most at risk this week?", "draft a response to that email", "what did I commit to delivering by Friday?" It knows your day.
The chat interface — examples
Chief of staff chat — live examples
Real queries, anonymised responses
Chapter 05
The outcome: every day starts with clarity instead of catch-up.
Since PersonalOS has been running, the morning pattern has fundamentally changed. The day no longer starts with an hour of context-gathering — it starts with a full picture already in hand, and the first hour is spent on work that actually moves things forward.
What changed
1hr
Recovered every morning
From context-switching to focused work
5hrs
Saved per working week
Compounding across every day
0
Missed deadlines since deployment
Overdue items surfaced before they become problems
9
Tools consolidated into one view
Without replacing or disrupting any of them
What it actually changed day to day
✓
Days start with intent, not reaction
The briefing arrives at 07:30. By the time the working day begins, priorities are already set. The first action of the day is the most important one — not opening Slack.
✓
Nothing important gets missed
Overdue tasks, blocked team members, and emails requiring action are surfaced every morning regardless of which tool they live in. The system reads everything so you don't have to.
✓
Industry intelligence arrives pre-filtered
Relevant AI and automation news is summarised with a note on why it matters to your current work — not a raw feed to triage, but a curated briefing with context already applied.
✓
Client conversations are better prepared
Walking into a client call with the latest relevant industry news pre-digested and applied to their situation is a material difference. The briefing makes that possible without any additional prep time.
✓
Available for other founders on request
Every PersonalOS deployment is bespoke — configured to your tools, your team structure, your priorities, and your voice. The core system is proven; the configuration is yours.
✓
Improves as your business evolves
The briefing prompt and integration set are updated as priorities shift. New tools can be added as integrations. The system grows with the business rather than becoming stale.