Side Quest

01GTM systems

Designed

Account Intelligence

Turn account signals into timely, relevant outreach.

A personal workspace for an enterprise rep: assigned accounts, a classified change, and a draft that cites that change.

The walkthrough below is sample data in this portfolio. It is not a deployed feed, and it does not call a model.

My role
Product design and GTM systems
Scope
Personal feed. Not a team admin console.
Technology
Next.js for this walkthrough. Supabase, Exa, Sumble, Claude are planned, not running here.
Explore the workflowView technical architecture

Account intelligence

Illustrative demo data

3Sample accounts

4Sample signals

Leadership change

Acme Corp

New VP of Application Security appointed.

Hypothesis, not a fact: they may review current tooling.

Try one example: Acme Corp: a signal and a next conversation

Guided example: Acme Corp: a signal and a next conversation

Synthetic walkthrough

Fictional account and announcement. No real citation, account upload, research feed, model call or outreach send is represented.

Step 1 of 4

Observe

Acme Corp appointed a new VP of Application Security. Illustrative company announcement. Not a real citation. Example date: September 2026.

Built with

Confirmed in the repository that renders this page. Planned tools stay in the case study and are not shown as logos.

02The problem

The problem isn't finding information. It's turning information into action.

A rep already has news, job posts, and CRM notes. What they lack is one place that says which assigned account changed, what was actually observed, and what to do next.

Before

  • Research split across feeds, sites, and CRM
  • The same accounts checked by hand every week
  • Territory list disconnected from the reason to call
  • Outreach that could have been sent to anyone

Designed outcome

  • A book limited to assigned accounts
  • A change tagged as funding, leadership, hiring, technology, or news
  • The observed fact kept separate from the hypothesis
  • A draft the rep can edit and copy, not an email that sends itself
Explore the workflow

03Product experience

From account assignment to a draft a person still has to send.

Four steps a rep would take. Territory mapping would decide which accounts belong here. This demo only shows when and why someone might reach out.

Account intelligence

Illustrative demo data

3Accounts in this demo

4Sample signals

Illustrative assigned accounts. Not a live territory.
AccountIndustryRecent signalsAction
Acme CorpFintech2 in demo
NorthstarSoftware1 in demo
MeridianHealthcare1 in demo

In the design, assignments would sync from territory mapping or be typed in. Neither sync exists in this repository.

Architecture and implementation

04System architecture

How the system would work.

Account Intelligence and territory mapping would keep separate databases and pass assignments between them. Solid pills are what this page actually does. Dashed pills are the planned product.

Data collection

Assignments would arrive from territory mapping or be typed in, then sit in this app’s own database. Exa and Sumble are the research sources in the design. None of those connections run here.

  • Territory mapping

    Planned

    Would send account assignments. The partner page is a design, not a live webhook.

  • Manual entry

    Planned

    A rep could add an account when no assignment exists.

  • Supabase

    Planned

    Planned store for accounts, signals, and drafts. Not a dependency of this site.

  • Exa and Sumble

    Planned

    Planned sources for public company changes. Not called from this repo.

Intelligence processing

Events would be normalized, tied to an assigned account, classified, and stored. This page classifies four sample rows by hand.

  • Normalize and classify

    Planned

    Funding, leadership, hiring, technology, or news. A person confirms the type.

  • Account association

    Planned

    A signal stays attached to one assigned account. Unmatched items do not enter the feed.

  • Signal storage

    Planned

    Planned records: signals and signal_feed_reads.

Sales activation

The feed and the draft on this page are a browser walkthrough. Copy works locally. Claude is not called, and nothing is sent.

  • Personal feed

    In this demo

    The sample list in the walkthrough above.

  • Claude draft

    Planned

    Planned. The demo swaps two local paragraphs instead.

  • Human review

    In this demo

    A rep checks the source before anyone sends.

  • Copy

    In this demo

    Copy draft writes the sample text to the clipboard.

Design decisions and tradeoffs

05Product decisions

Designing for a focused MVP.

Personal feed before team admin

The first version is one rep’s book and their drafts. Manager views and shared settings wait.

Its own database

Territory mapping and this feed would each keep their own records, and pass assignments across. Either one can exist if the other is down.

Copy a draft before a sequencer

The test is whether a rep uses a draft that cites a real event. Nooks or Outreach comes after that, not in v1.

Technical notes

Planned records. accounts, rep_assignments, signals, signal_feed_reads, outreach_drafts.

MVP question. Does a personal feed make outreach cite a specific event, or do reps still send the generic note?

Out of scope for v1. Live Nooks or Outreach, multi-rep admin, and Salesforce IDs.

06Outcomes and roadmap

Measuring what matters.

Proposed success metrics. I do not have usage data. The comparison I would run: similar accounts, one note that cites a documented signal and one that does not, then look at reply quality — not just sends.

System reliability

  • Assignment sync succeeds
  • A reviewed signal keeps the right type and account

Proposed. Not measured.

Rep adoption

  • Reps open the feed
  • Drafts copied after a person edits them
  • Less time rebuilding the same account brief

Proposed. Not measured.

Business outcomes

  • Share of notes that cite a signal
  • Reply and positive-reply rate
  • Meetings from those threads

Proposed. Not measured.

  1. Designed now

    • Personal feed
    • Classified signals
    • Source kept next to the event
    • A draft a person reviews

  2. Next

    • Better ranking of signals
    • More public sources
    • A sequencer only after drafts get used

  3. Later

    • Multi-rep view
    • Team analytics
    • CRM identifiers

“Designed now” is the scope of the concept. The only part you can click is the sample walkthrough on this page.

Connected GTM systems

Territory and ownership

Partner GTM Engine

The channel design for who owns an account. It would hand assignments to this feed. It is not deployed.

When and why to engage

Account Intelligence

This page. It watches the assigned book and turns one observed change into a draft the rep still has to send.

Explore related work

Back to all projects