Variance Questions Start as Email, Not Planning Models

The model is in the ERP; the story starts in Gmail

Finance transformation slides love a single planning surface. Month-end reality is messier: the CFO forwards a screenshot, asks whether marketing pull-forward explains the variance, and wants an answer before the board prep call. That question is not big enough to rebuild a model. It is big enough to eat an afternoon if nobody distills the thread.

Investor relations adds another loop: bridge narratives between GAAP results and operating metrics often start as half-formed questions in mail, then become slides under deadline pressure. The work is language plus structure, not arithmetic alone.

<a href="https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/superagency-in-the-workplace-empowering-people-to-unlock-ais-full-potential-at-work" target="_blank" rel="noopener noreferrer">McKinsey writing on superagency</a> keeps tying AI value to workflow redesign. For FP&A, redesign often means fewer round trips between the inbox and the deck, not another login. <a href="https://www.oecd.org/content/dam/oecd/en/publications/reports/2024/03/using-ai-in-the-workplace_02d6890a/73d417f9-en.pdf" target="_blank" rel="noopener noreferrer">OECD survey evidence on AI in the workplace</a> notes both uplift and intensity when throughput rises without clearer ownership—exactly the risk when everyone can draft faster but nobody owns the number.

<a href="https://www.hbs.edu/ris/download.aspx?name=w33795.pdf" target="_blank" rel="noopener noreferrer">HBS generative AI at work research</a> supports embedding assistance where people already coordinate. <a href="https://hbr.org/2019/01/how-to-spend-way-less-time-on-email-every-day" target="_blank" rel="noopener noreferrer">Harvard Business Review guidance on email</a> is the practical anchor: batching is hard during close week. <a href="https://www.mckinsey.com/~/media/mckinsey/business%20functions/mckinsey%20digital/our-insights/seizing%20the%20agentic%20ai%20advantage/seizing-the-agentic-ai-advantage.pdf" target="_blank" rel="noopener noreferrer">McKinsey materials on agentic advantage</a> stress cross-functional rewiring—claims, sales, and ops all show up in the same variance mail. <a href="https://aiindex.stanford.edu/report/2025" target="_blank" rel="noopener noreferrer">Stanford AI Index</a> is macro context: spend is hot, proof is uneven; your metric should be hours and error rate.

What to hand off without handing off control

Distill to Three at distill.to.three@via.email turns a forty-message cross-functional chain into bullets for the CFO readout. Extract Action Items at extract.action.items@via.email captures follow-up metric requests so they do not die in paragraph four. Recap Call Notes at recap.call.notes@via.email converts messy close call notes into a structured follow-up you still edit. Draft Payment Reminder at draft.payment.reminder@via.email helps when the variance story is really a collections story with better clothes. Audit SaaS Contract at audit.saas.contract@via.email supports vendor true-up questions that arrive as a PDF and a panic subject line.

via.email processes text and attachments you provide in mail. It does not log into your ERP, send email for you, or remember a different thread from last quarter.

When the board deck is due, the highest leverage move is often structural: turn the mail thread into a short list of drivers, open questions, and requested follow-ups before anyone opens PowerPoint. The deck still needs human judgment. The thread stops being the place where facts go to hide.

The guardrail that matters

Assistants should tighten language around numbers finance already owns, not invent causal stories from vibes. If the model did not see the workbook, it does not get to claim the bridge from revenue timing to headcount. Use drafts as scaffolding; controllers still sign.

A close-week rhythm that fits the way you already work

Sunday night: drop the escalation inbox through Distill to Three so Monday staff meeting starts with decisions, not rereads. Tuesday: run Extract Action Items after the revenue review so follow-up metric pulls do not live in paragraph six. Thursday: Recap Call Notes after the exec session so board prep inherits one coherent memo instead of four partial forwards.

Cluster reading

Invoice-heavy finance mail is its own lane in Finance Teams: Invoice Extraction and GL Coding in Email. For executive communication load, When Leaders Send Less Mail, Everyone Else Breathes. names the amplification problem. When tool sprawl eats gains, Productivity Beyond Three: When More AI Tools Start to Hurt. explains the cognitive tax in parallel.

Variance is a narrative sport

FP&A credibility is speed plus accuracy in plain English. via.email keeps drafting and extraction inside the channel the CFO already monitors, without pretending a planning UI is the only honest place to think.

The end state is not fewer emails. It is fewer ambiguous emails. When everyone works from the same extracted spine of owners and dates, you spend less time reconciling interpretations and more time reconciling numbers—which is the job you were hired to do.

If you want a cheap cultural signal, watch whether people stop forwarding chains with no subject change except RE: RE: RE:. Structure is a kindness to the next person in the rotation. Controllers still own the sign-off; the goal is fewer midnight rewrites, not fewer controls.