Effortless Team Alignment (ETA)

What we built

Effortless Team Alignment (ETA) is an email-first operational intelligence assistant for back-office teams. It turns work that people deliberately share with a department agent into a visible operating picture, clear next actions, and system-generated follow-through—without reading an organization’s mailbox or building a public employee scorecard.

This runnable demo follows an Accounts Payable supervisor, Jordan, from a blank slate. Jordan receives a supervisor invitation, sends an editable plain-English setup email, confirms the proposed seven-person AP team and its operating model, then introduces the department agent, Simon, to the team. The Command Center exists only after that deliberate setup is complete.

The problem

AP work is spread across invoice intake, matching, approvals, payment runs, remittances, expenses, reconciliations, and close. Critical handoffs and evidence get lost in email, so managers become the follow-up system. Existing tracking tools often create another destination people must learn—or make individuals feel watched.

How ETA works

ETA uses a different contract: it only works from messages people intentionally send, copy, forward, or reply to it about. Simon is visibly the sender of every ETA-generated follow-up. A worker is never made to appear to have sent a message they did not send.

The demo then follows Andy, an AP specialist. He receives his July AP plan, opens a private ETA workspace containing only work deliberately assigned or shared with him, and reports that invoice BC-1042 is blocked because the receiving record is missing. ETA records that update, keeps it source-linked, identifies the next handoff, and prepares a clearly system-generated coordination request.

What makes it different

Setup begins in email, not a pre-populated dashboard. The supervisor establishes the department and operating model deliberately.
Email-first without surveillance. ETA does not connect to or monitor the organization’s mailbox.
Process health, not people ranking. Shared views expose stalled work, risks, and dependencies anonymously. Named detail is limited to the individual and authorized manager who need it to act.
Completion is confirmed, not assumed. A worker can submit evidence, but work is only marked complete when the responsible receiving or approving party confirms it.
Coordination is transparent. ETA sends from its own identity, identifies responsible parties, and lets them control notification preferences.

How we used Codex and GPT-5.6

We used Codex with GPT-5.6 throughout the project to turn the product concept into the PRD, trust model, AP workflow map, information architecture, interaction model, runnable screens, demo-state logic, and the testable local application. Codex accelerated the design-to-code loop, including the supervisor setup flow, employee workspace, email simulation, privacy boundaries, and scenario data.

In the production architecture, GPT-5.6 is the reasoning layer that would understand deliberately shared messages, extract source-linked operational proposals, surface relevant dependencies, and prepare context-aware coordination requests. The submitted demo intentionally uses deterministic local data so judges can run the full story without credentials.