School email intake
Forward a school message to Marlow and let it extract the dates, deadlines, excursions, forms, and follow-up tasks that matter.
Product
What Marlow actually does.
Marlow is built around one core job: turning messy incoming family logistics into trustworthy follow-through.
The wedge
Not just a smarter calendar.
The real work happens before something ever reaches the calendar. Marlow handles the inbound messages, links, changes, and deadlines that create the admin burden in the first place.
Core flow
How Marlow fits into a busy household.
-
1. Inbound message arrives
A school email, newsletter, payment reminder, or schedule change lands in email or chat.
-
2. Marlow reads and classifies it
It pulls out dates, deadlines, forms, costs, links, and who the message is about.
-
3. Marlow decides what to do
It can create a reminder, propose a calendar update, save context for a briefing, or ignore the item based on family preferences.
-
4. The family gets a calm summary
Instead of a raw dump, Marlow explains what changed, what matters, and what still needs action.
-
5. The system gets smarter over time
Marlow remembers household preferences like what to ignore, what to highlight, and when to ask for confirmation.
Capabilities
The first things Marlow should be genuinely good at.
Calendar updates
Marlow should be able to add or update events when a message is clear, and ask when something needs confirmation.
Reminder and task creation
Payment due? Permission slip needed? School photos tomorrow? Marlow should turn those into action, not just awareness.
Preference learning
Ignore routine sports notices. Highlight payment deadlines. Summarize newsletters. This is where the assistant starts feeling personal.
Daily and weekly briefings
Marlow’s signature surface is the briefing: what changed, what matters now, and what the household should be aware of next.
Family-aware memory
Marlow should know which child a message relates to, what the family usually cares about, and where uncertainty still exists.
Example
From a school email to organised action.
A parent forwards an email about an excursion. Marlow reads it, checks the details, identifies the due date, and notices it applies to one child. It adds the event, creates the payment reminder, and includes the result in the next briefing.
- Identify the child and school context
- Extract dates, deadlines, forms, and costs
- Handle reschedules and corrections
- Explain what it changed and why
Product example
Friday school intake
- Excursion moved from Wednesday to Thursday
- Payment due date added to reminders
- Sports notice left out of main briefing
- Parent asked to confirm one unclear pickup detail
Assistant-first
Works where families already are
Email, chat, and calendars are the primary surfaces. A standalone app is not the prerequisite for value.
Trust-aware
Confirmation when uncertain
Marlow shouldn’t quietly make risky changes. It should be clear when something is obvious and careful when it’s ambiguous.
Family-aware
Built for household context
Which child? Which school? Which notices should be ignored? Those are the kinds of things Marlow is meant to keep track of.