Professional field practice

Project 03

01Competitive strategy and GTM systems

Used professionally

Competitive Intelligence Engine

Know what changed. Understand why it matters. Act with confidence.

For sellers answering technical comparison questions, I developed briefs and field guidance that connect a claim to its source and a useful discovery question. This example explores how Sales, Product, and Product Marketing could share that review process. The aim is to make expertise easier to reuse and help buyers understand the tradeoffs. Field briefs were used with teams; the monitoring workflow here is a design.

Role
I wrote competitive briefs and taught the guidance; this page illustrates the proposed software workflow.
Stage
Field-system foundation. Monitoring is designed, not software in this repository.

Intelligence workspace

Example data

Example providers
5
Sources reviewed here
1
Live monitors
0

Recent example

TruffleHog · product capability

An illustrative sentence pair, not a historical vendor change. Review status: needs a person.

Available brief: Detection is not verification.

View details
Built with

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

02The intelligence problem

Competitive knowledge changes. Static battlecards do not.

Before

  • Competitor notes scattered across deals
  • Decks that go stale after the meeting
  • Claims with no source and no date
  • The useful detail stuck with one seller
  • The same public page read twice

Designed

  • A profile per provider, with what is not evaluated left blank
  • A short list of public sources, not the whole web
  • The original page and review date kept on the claim
  • Field guidance only after a person approves it
  • One brief another rep can teach
Explore the workflow

03Product experience

From a competitor change to field execution.

Explore five steps from source review to a field brief. The walkthrough uses example providers and a reviewed public TruffleHog source.

Provider dashboard

Example data

Session takeaway · illustrative only

What this example helps you decide

Provider under review
TruffleHog
Available evidence
Public repository reference, not a live monitoring feed
Change review
Not marked reviewed
Impact hypothesis
Not marked reviewed
Suggested question, not an approved claim
Which credential types do you verify live, and which have you not evaluated?
Remaining unknowns
Specific detector coverage, current competitor differences, and customer impact have not been independently verified.

0 field notes marked approved for this session. This summary is generated only from current browser memory. Nothing is saved, sent, published, or approved for real-world sales use.

Optional practice

Practice the evidence habit

The five-stage workflow above is the main interactive demonstration. This separate four-step exercise is an optional teaching example for inspecting a source, distinguishing interpretation, and drafting a field question. It does not update the workflow or approve a claim.

Try one example: From a source to a field question

Guided example: From a source to a field question

Synthetic walkthrough

The current line names verification as its own step. Both lines were written for this walkthrough. They are not a stored crawl and not a historical vendor diff. No monitoring job runs here and no competitive claim is approved by completing this example.

Step 1 of 4

Inspect the reference

Public repository description. Date: Illustrative. Not a detection timestamp.

Public repository reference (opens in a new tab) ↗
Architecture and implementation

04System architecture

How the intelligence system would work.

Four stages show how the field process connects to a proposed software workflow. This repository does not use Firecrawl, Exa, a GitHub API client, or a model.

What the status labels mean

Professional field system
Briefs and review practices used with teams.
In this walkthrough
Illustrative behavior or sample content on this page.
Planned
Proposed capability.
  1. Source collection

    Field briefs were written from public pages and deal notes.

    • Official websites

      Professional field system

      Read by hand for briefs. Not crawled here.

    • Product documentation

      Planned

      Proposed input.

    • Release notes

      Planned

      Proposed input.

    • Public GitHub repositories

      In this walkthrough

      One cited URL. No GitHub API client.

  2. Change intelligence

    The walkthrough shows a hand-written pair of sentences. Nothing is scheduled, snapshotted, or classified by software.

    • Scheduled monitoring

      Planned

      Proposed capability.

    • Source snapshots

      Planned

      Not stored.

    • Change detection

      In this walkthrough

      Illustrative pair only. Not a diff.

    • Classification

      In this walkthrough

      One category, chosen by hand.

    • Source attribution

      In this walkthrough

      The public URL stays on the claim.

  3. Human review

    Recommendations do not approve themselves. A model is not called.

    • Evidence verification

      Professional field system

      Briefs used with teams were reviewed by a person. Those files are not in this repo.

    • Impact analysis

      In this walkthrough

      A written hypothesis you can mark reviewed.

    • Approved findings

      In this walkthrough

      One teaching claim on this page.

    • Recommendation review

      Planned

      Proposed review queue.

  4. Field activation

    Battlecards were documents. Alerts, CRM context, and change history are later.

    • Competitive profiles

      Professional field system

      Briefs and playbooks used with teams. Not this app.

    • Battlecards

      In this walkthrough

      The sample brief in the walkthrough.

    • Alerts

      Planned

      Proposed capability.

    • Field feedback

      In this walkthrough

      A form that stays in the browser.

    • Change history

      Planned

      Not stored.

Design decisions and tradeoffs

05Product decisions

Designing for trustworthy intelligence.

Evidence before interpretation

A claim keeps the original source and the review date. A sentence without those two is not ready for the field.

A person approves the guidance

Change detection can point at a diff. It cannot approve what a seller is allowed to say.

A short list before broad coverage

Start with a few providers and sources that can be checked. An empty cell stays empty.

Technical notes

Planned records. Competitor, Claim, Change, Impact, Recommendation, Deal context.

MVP question. Does a shared brief change how a deal is run more than a one-off deck?

Out of scope. Scraping the entire internet, and automated public attack content.

06Outcomes and roadmap

Measuring intelligence quality and field adoption.

Proposed success criteria. Nothing below has been measured in this repository.

System reliability

  • Source monitoring coverage
  • Change detection latency
  • Evidence completeness

Proposed. Not measured.

Intelligence quality

  • Time to human review
  • Percentage of findings approved
  • Battlecard freshness

Proposed. Not measured.

Field adoption

  • Brief usage
  • Field feedback submissions
  • Competitive opportunity usage

Proposed. Not measured.

See the roadmap
  1. Professional field system

    • Structured competitor profiles
    • Source-backed battlecards
    • Reusable field briefs
  2. Next

    • Scheduled source snapshots
    • Change detection
    • Human-reviewed updates
  3. Later

    • Field alerts
    • CRM opportunity context
    • Product feedback integration
    • Historical change analytics

Explore related work

Back to all projects