Skip to content
Emilyby The Architect LabStart with an audit
Start with an audit

Selected examples

Real problems, configured assistants.

Each example shows how Emily is configured around one recurring operational failure. All examples use fictional companies and data, and say so.

01Operations · Handover · ContinuityExample configuration

Someone’s leaving Friday. Emily already knows what they forgot to hand over.

The unsigned contract. The invoices nobody chased. The four tasks everyone quietly assumed were somebody else’s problem. Emily writes the handover and sticks around while you’re gone. Doesn’t even want a thank-you card.

View example
EmilyHandover briefing — Friday 17:00
  • Open items across systems14 foundWatching
  • Approvals due before Friday3 waiting on youNeeds you
  • Supplier invoices2 not yet receivedMissing
  • Venue contractUnsignedMissing
  • Tasks without a confirmed owner4 proposed reassignmentsWatching
  • Client deadline during absence1 — cover note preparedReady
  • Drafted follow-upsReady, nothing sentReady
Example configuration — fictional data

02Projects · Scope · ApprovalsExample configuration

Every brief and approval in one place. Emily is almost offended this wasn’t already true.

What was promised. What changed. What’s stuck. What’s next. One record, not six apps and Steve’s memory. Steve left in March.

View example
EmilyProject record — Meridian rebrand
  • Brief v3 approvedClient email · 4 JuneReady
  • Motion added to scopeCall note · not in feeNeeds you
  • Round 3 feedbackReceived · 2 items unresolvedWatching
  • Guidelines deadlineFriday · on trackReady
  • Photography approvalWaiting on client · day 6Missing
  • Change-of-scope noteDrafted for reviewReady
Example configuration — fictional data

03Events · Finance · AdministrationExample configuration

The event’s over. The paperwork, shockingly, is not.

Offers, contracts, invoices and sign-offs, tracked from the first over-optimistic phone call to a closed P&L. Your accountant will not know how to process the calm.

View example
EmilySettlement — Northbank Festival
  • Artist offers agreed12 of 12 · documentedReady
  • Contracts signed11 of 12 · 1 unsignedMissing
  • Supplier invoices23 received · 4 expectedNeeds you
  • Rider costs (informal)2 without paperworkWatching
  • Awaiting approval to pay3 items · £14,180Needs you
  • P&L status82% closedWatching
Example configuration — fictional data

04Clients · Reporting · GrowthExample configuration

The client relationship survives even when the account lead doesn’t.

The history. The stakeholders. The thing they mentioned once that everyone forgot except Emily. She has it ready before you sit down. You’ll look prepared. You have no idea why.

View example
EmilyPre-meeting brief — Arlo & Grey, Thursday 10:00
  • Last contact9 days ago · coverage reportReady
  • Open commitments2 · one due this weekNeeds you
  • Stakeholder changeNew marketing directorWatching
  • Unresolved from last meetingQ3 budget confirmationMissing
  • Preference on recordNo Friday announcementsReady
  • Opportunity flaggedProduct launch in OctoberWatching
Example configuration — fictional data

05Scope · Margin · ApprovalsIllustrative workflow

Every change of scope gets noticed before it gets expensive.

Emily watches the distance between what was agreed and what is being done, and flags the gap while it can still be charged for.

Detailed page in preparation

06Leadership · Visibility · DecisionsIllustrative workflow

The morning view of everything that actually needs you.

A daily briefing across every project, account and deadline: what changed, what is at risk, what is waiting on a decision — instead of an hour of reading threads.

Detailed page in preparation

Your operation will not match these exactly. It is not supposed to.

Every assistant is configured during a build, around the systems and rules of the business it serves.