Alto Foundry

Back to Archer to see the app, pilot it with one team, or read how it handles your meetings.

Alto FoundryArcherRedactAIPrivacySecurityTermsLegal

Your path

What you've seen and chosen so far. At the end, this is what we email you with the Blueprint.

T01

Symptoms at the waterline

Pick a symptom

The eight symptoms sit above the waterline, each wired to the cause underneath that feeds it. Pick one: the rest fade, its line lights and a pulse runs down to the cause.

What you seeWhich of these do you see?

Below the waterline
T02

Your map so far

Where next (hub)

The hub keeps the waterline. The symptom you came in by sits above it, wired to the cause you explored; the other causes wait below. Press Dive here to send a pulse down.

Where nextYour map so far

Below the waterline
T03

Minimise dependencies

Dependencies · Principle

The principle wipes in on a teal panel, then steps aside for one outcome's delivery timeline. Tap a team to delete that dependency: its wait and its meetings vanish, and lead time rolls down from 14 weeks to 3.

A principle you can follow

Minimise dependencies.

Lead timeweeks
Syncs a week

Every dependency turns into a meeting.

Waiting on · tap to delete

T04

Decisions find the information

Decisions · Principle

After the principle lands, a small decision climbs the ladder one meeting and a few days at a time, then trickles back down. Flip “Push it down” and it resolves where the information already is.

A principle you can follow

Move decisions to where the information is.

D
The decision

Trial a new supplier for one monthReversible. The team has the numbers.

Up the ladderPushed down Days Meetings

T05

Only what needs the room

Bad meetings · Principle

A 60-minute meeting, drawn to scale. Tap any agenda item that could be written down and it flies into the doc, with Archer suggesting which ones; the meeting shrinks to the 20 minutes that need people together. Tap a doc line to put it back.

A principle you can follow

A meeting is for what can only be done together.

Tue · Leadership sync6 items

min10:00 to 11:00
Archer suggests

Trade-offs, disagreements, decisions. Everything else can be written down.

Write it down

    Nothing yet.

    T06

    Two hours, six months

    Dependencies · One lonely item

    The plan goes green, bar by bar, except one. The camera follows that item into the other team’s queue, where ten teams’ tickets sit ahead of it: two hours of work, twenty-six weeks of waiting. Replay to watch it again.

    Delivery plan · 0 of 8 done

    Platform team queue

    10 teams ahead of you

    012hours of work
    versus
    0
    weeks waiting

    One dependency, one scheduling dance. 26 weeks later.

    T07

    A room of 100

    Bad meetings · The evidence

    A hundred people in one meeting, recoloured by each finding in turn while the number rolls. The last finding turns the people into meetings and strikes out the ones nobody needed. Step through with 01, 02, 03 or let it run.

    100 people in a meeting

    of 100

    T08

    Two doors

    Decisions · Two kinds of decision + Try it

    Amazon’s one-way and two-way doors, built as real doors. Drag each decision onto the door it belongs to: the heavy one unbolts and swings shut with weight, the light one swings and flaps back. Wrong door, the card bounces back with the reason.

    Drag each decision through its doorDrag each card to its door
    0
    ONE-WAY
    One-way doorHard to undo

    0
    Two-way doorCheap to undo
    T09

    The single-threaded team, by Amazon

    Dependencies · The single-threaded team

    Sixteen people, each striped in the colours of the initiatives they’re split across, tangled to four goals. Press “Single-thread it” and everyone regroups into four one-colour teams under one leader, and the quote lands. Toggle back to feel the mess again.

    16 people, 4 initiatives. Nobody works on just one.

    The best way to fail at inventing something is by making it somebody’s part-time job.
    Working Backwards · Bryar and Carr
    T10

    The myth, struck out

    The assumption it breaks · all three causes

    The thing people say types in huge, a red line strikes it out and the rebuttal wipes in. Beside it, a live proof of why it fails: a steering committee that jams the network, an inbox that piles up, a room whose bill keeps rising. Switch the myth off to see the fix; tabs switch cause.

    The assumption it breaks

    “

    T11

    Your dependencies, in your calendar

    Dependencies · A question for you

    Your team sits in the middle. Press + for every team you need time from to deliver one outcome: each one joins the orbit, drops a recurring 30-minute sync into your week, and the hours roll up.

    Teams you need time from
    0for one outcome
    0123456789½

    The test: if my team’s work needs effort from yours, to build, take part or review, you’re one of my dependencies.

    T12

    Swipe the waiting pile

    Decisions · A question for you

    The decisions waiting on you this week, as a stack. Swipe each one left if it can’t be undone, right if it could be undone next week. The piles fill, and the count tells you how much could be pushed down.

    Can’t undo0
    ← Swipe left
    Waiting on you this week
    Could undo0
    Swipe right →
    T13

    Write the outcome

    Bad meetings · A question for you

    A real invite with one field that matters. As you type, a live judge tells an activity from an outcome, underlines the giveaway word and resizes the meeting to fit. Try the examples, or write your own next meeting.

    InvitationTue 10:00 · 6 guests
    Your next meeting
    Length
    Live check

    If you can’t write it, the meeting probably doesn’t need to happen.

    T14

    Your week, before and after

    What can be done · all three causes

    A real-looking week starts full, then empties. Drag the handle to compare before and after, and switch each fix on to watch its meetings vanish or shrink while the hours-back counter rolls up.

    Mon19Tue20Wed21Thu22Fri23
    BeforeAfter

    Hours back this week

    In meetings →

    Problems Archer tackles

    One person’s week · illustrative

    T15

    Why: I’ve sat in that calendar

    About us · Where this started

    Andy’s story as a short film: the department, the hours, a payroll receipt that prints out to 70%, then the flip to teal and why we built Archer. Tap the progress bars to jump to any beat.

    Where this started

    Each dot ≈ 35 people

    Andy was consulting with a company with

    0employees.

    Onedepartment.

    5 to 6 hours a dayin meetings.

    9am5.5 of 8 hours5pm

    When we puta cost on it.

    One departmentOne day

    Working day8 h

    In meetings5–6 h

    Each one bookedfor a reason

    The real workin the gaps

    ≈70%of payroll

    Most of these meetingscould be changed.

    We decided tobuild Archer.

    Meeting intelligence software to cut the coordination tax.

    Andy Wetherell · Alto Foundry

    T16

    Archer in use

    About us · What we’re building

    A scripted walkthrough of the real app, like a video but live HTML: a cursor names an outcome, sends a standup async, opens a Brief for me and supersedes a decision. Click any chapter to jump, or pause to read.

    PArcher
    Today
    Meetings
    Standing
    Decisions
    Metrics

    Transcribed on the device · No audio stored

    T17

    The design partner offer

    About us · The offer

    The pilot offer in three numbers, with a short express-interest form.

    Limited design partner places

    Pilot Archer with one team. See the hours come back.

    8weeks

    One team or department, ending with an executive readout

    50% off

    Every seat during the pilot: $25 a user a month, not $50

    30% off

    Every seat for the rest of year one, new ones included

    $1,000for the 8-week pilot $2,000

    Up to 50 users in the pilot. Nothing renews automatically. Prices in AUD ex GST.

    Design partner pilot

    Express interest

    Leave your details and we’ll be in touch about a pilot place.

    Thanks, we’ve got your request.

    We’re keeping the first group of design partners small, so we review every request before offering a place. Andy will email you personally within 5 business days.

    What happens next

    1. Read the Design Partner Pack. It covers the 8-week pilot, the pricing and what your team would see. Open the pack (PDF)
    2. Think about where you’d start. Andy’s first questions will be which team you’d pilot with, and the standing meeting you’d most like to win back.

    Rather talk now? Email hello@alto-foundry.com.au

    T18

    Who's building it

    About us

    The two founders as linked nodes, what they've done, how Alto Foundry works, and when the first pilots start.

    Who’s building it

    We’ve sat in these meetings. Now we’re building the way out.

    Archer comes from Alto Foundry, an independent product R&D lab. We build AI products for enterprise: for organisations whose work is complex and whose information is sensitive, where generic software doesn’t fit.

    • 01Takes work awayNothing new to log into and no manual entry. Archer removes work rather than adding a system.
    • 02Fits how you already workWorks with Teams, Zoom and Outlook today.
    • 03Security is architectureTranscribed on the device with no audio stored, hosted in Australia or in your own cloud.
    Andy Wetherell

    Andy Wetherell

    CEO · Alto Foundry

    • DefenceBuilt large-scale innovation training
    • ConsultingWorked inside the 20,000+ person enterprise in this story
    Jas Hayer

    Jas Hayer

    CTO · Alto Foundry

    • AWSSenior Solutions Architect, Asia Pacific and Japan
    • AccentureTechnology Delivery Manager
    Together at Alto FoundryAlready delivering AI software for healthcare and Defence
    October 2026First design-partner pilots start, each with one team for eight weeks.

    Also from the lab: RedactAI, for preparing safer documents with AI.