BringTrade Bid Strategy Desk
Mike-only clickable pilot mockup

One messy ITB becomes a clean strategy card.

This is the paid proof sprint: turn real bid invites into cards, call lists, recommendation shelves, protocol capture, Julie scripts, and response timelines.

If we can make one Julio-style opportunity clean and actionable, then we can scale it. If we cannot organize one, we should not pretend we can automate fifty.
Prototype note: Buttons show the intended workflow only. Nothing sends, saves, or contacts anyone from this mock-up.

Phase 0 deliverables

The $1,000 ask becomes artifacts, not theory.

3–5real ITBs organized
1recent contact call list
1Mike protocol capture
1Julie script + outcomes

How to Read This Mockup

This is a prototype of the BringTrade Bid Strategy Desk. It is not a live CRM or automation yet. The goal is to show how one messy ITB can become a clean strategy card, call list, recommendation shelf, response timeline, and Julie script.

Prototype guide
Prototype only: buttons show the intended workflow and do not send, save, or contact anyone.
Mike Dashboard

Shows the pipeline view: what needs Mike, what is ambiguous but alive, and what is ready to call.

Opportunity Card

Turns one messy ITB into a clean page with project, contact, scope, deadline, missing info, and suggested decisions.

Recommendation Shelf

Shows the best possible plays: ask for protocol, request plans, route to electrical, add to call list, or park.

Response Timeline

Shows what happened, who approved it, what changed, and what the next state is.

Call List

Turns phone numbers into logged intelligence instead of dead labor.

Protocol Capture

Captures Mike's judgment so the system knows what is worth chasing and what Julie is allowed to ask.

Julie Loop

Shows how Julie helps safely: approved questions, outcome buttons, and escalation rules.

Phase 0 Ask

Shows what the $1,000 proof sprint produces.

Your judgment becomes the protocol. The protocol becomes Julie's script. Julie's outcomes become the system's learning.

Mike’s Dashboard

Not another spreadsheet. A cockpit for bid content, decisions, calls, and next plays.

Sample pilot view

Needs Mike

3

Approve a message, decide fit, assign call, or park.

Ambiguous alive

5

Bid date passed, unclear reply, missing plans, or portal blocked.

Ready to call

12

Recent ITB contacts with phone/email and call reason.

Active opportunity cards

OpportunityStatusBest current play
Julio / BuildingConnected ITB
Electrical + possible GC/sub posture		Ambiguous aliveAsk what protocol Julio wants now
Recent ITB Batch
Phone outreach list		ReadyMike calls / Julie logs outcomes
Portal-only invites
Plans trapped behind BC		BlockedAsk for direct plan access or invite

What this replaces

Excel alone
Rows without memory, protocol, call outcomes, approvals, or suggested plays.
Email alone
Threads get buried; no clear state, no node map, no timer.
Strategy Desk
Every bid has content, protocol, recommendations, call list, timeline, and next action.
Core doctrine: Mike’s judgment becomes the protocol. The protocol becomes Julie’s script. Julie’s outcomes become the system’s learning.

Opportunity Card: Julio / BuildingConnected ITB

The single truth page for one messy bid opportunity.

Ambiguous but alive

Bid content

ContactJulio — GC-side bid coordinator / “super GC” contact
SourceBuildingConnected ITB email thread
TradeElectrical first; possible Mike GC/sub angle
Deadline stateBid date appeared passed, but Julio replied that bids are being taken seriously
Current problemHope created, then silence. Need protocol clarification.
GoalFind out if bids are still useful and how Julio wants them submitted.
Flag: Julio’s reply functioned like a soft reopening without formally extending the deadline.

Protocol + decision buttons

Commands govern the field. Suggestions move the play forward.

Command needed
BuildingConnected only? Direct email? Required bid form? Scope sheet? License/insurance?
Strategy
Ask Julio how to comply instead of guessing.
Outbound posture
Mike is willing to work as a disciplined subcontractor under Julio’s process.

Outbound draft to Julio

Approval gated

Julio — thanks again. We want to follow your process correctly and not guess at your standards. Are late bids still being reviewed for this package? If yes, what is the correct protocol now: BuildingConnected only, direct email, required scope sheet, exclusions, license/insurance, deadline, or any preferred format?

Recommendation Shelf

Given the current state, here are the 3–5 best plays. Not random reminders — strategic options.

Play battery

Play 1: Ask Julio for protocol

High priority

Best because the bid date is confusing and Julio already signaled bids may still matter.

Play 2: Request direct plan access

High priority

If plans are portal-only, ask for a direct link or invite for the right estimator.

Play 3: Route electrical to Tony

High fit

Tony is a cleaner trade fit for electrical ITBs. Mike can still evaluate GC/sub posture.

Play 4: Mike call follow-up

Medium priority

If phone number exists, Mike can call personally and Julie logs the outcome.

This is the engine: protocol answers + email state + call outcomes create better recommendations next time.

Response Timeline / Node Map

This is the “email has no dashboard” answer: what happened, who approved, what was sent, what changed.

State history
1

ITB received

BuildingConnected invitation comes in. System extracts project, contact, deadline, trade, plan access, and missing fields.

state: raw_itb_received
Raw content
2

Kory routes to Tony / Mike

Electrical looks like Tony first; Mike may still have a GC/sub angle. System creates fit questions.

state: partner_fit_unclear
Needs strategy
3

Julio replies positively

Julio says bids are being taken seriously even though the date looked passed. Opportunity becomes ambiguous but alive.

state: ambiguous_alive
Alive?
4

Suggested protocol ask created

System recommends: ask whether late bids are still reviewed and what submission protocol Julio requires.

state: suggestion_pending_approval
Ready
5

Next state depends on response

Julio can answer: still open, closed, BC only, email me, need scope sheet, wrong contact, or future bids only.

state: waiting_response
Timer on

Recent ITB Call List

Mike asked for phone numbers. The win is turning every call into logged intelligence.

Call salvo
ContactPhoneEmailCall reasonLog outcome
Julio / GC bid desk(placeholder)julio@placeholder.comConfirm late bid protocol
Recent ITB Contact A(placeholder)bids@placeholder.comAsk if GC still needs subs
Recent ITB Contact B(placeholder)estimating@placeholder.comRequest plan access / scope
Recent ITB Contact C(placeholder)precon@placeholder.comAsk whether Mike can price as sub

Outcome taxonomy

Why this is not dead labor

A raw phone list dies after Mike calls it. A logged call list becomes system memory: which GCs are alive, who needs subs, what they ask for, what language works, and what Julie can safely ask next time.

Bridge to Julie: Julie does not need 21 years of judgment on day one. She needs approved questions, outcome buttons, and escalation rules.

Protocol Capture

This is not homework. It is Mike’s judgment extraction layer.

Training data

Mike protocol capture

Julio protocol capture

Message to Julio: “This optional survey helps us bring you better bidders, better questions, and cleaner bids according to your standards.”

Julie Training Loop

Mike’s 21 years do not get replaced. They get converted into protocol and scripts.

Approval gated

Training chain

1. Mike defines judgment
Fit, disqualifiers, call timing, hot lead signs, unsafe promises.
2. Protocol becomes script
Julie only asks approved questions and logs outcomes.
3. Outcomes become learning
Every call response improves the next recommendation shelf.
4. Exceptions escalate
Unclear, technical, or risky responses go to Mike/Kory.

Approved starter script

Hi, this is Julie with BringTrade calling on behalf of Mike. We saw your recent invitation to bid and wanted to confirm whether you are still accepting bids for this scope. If yes, what is the best way to receive plans and submit correctly?

Guardrail: Julie does not price, promise, negotiate, or represent Mike’s technical judgment without approval.

Phase 0 Funding Ask

The mockup shows the engine. Julio is the first real fuel. Mike pays for the engine to run.

$1,000 proof sprint

What Mike gets for $1,000

1Organize 3–5 real ITBs into strategy cards
2Extract recent ITB contacts into a call list
3Create recommendation shelves for each opportunity
4Create response timeline / node map
5Create Mike protocol capture for his qualification logic
6Create Julio protocol capture for the first live opportunity
7Create Julie call script and outcome taxonomy
8Identify what should be automated in Phase 1

Exact words to Mike

Mike, I mocked up the shape of what I mean. This is not just a phone list or spreadsheet. It is a Bid Strategy Desk. Each opportunity becomes a card: project, contact, scope, deadline, missing info, suggested plays, call targets, ready-to-send follow-ups, and decision buttons.


The phone list is doable, but I am not interested in it as dead labor. The value is that every call result gets logged: which GCs are alive, who needs subs, what they ask for, what follow-up wins. That is how the system gets smarter without Julie needing 21 years of your judgment on day one.

Close: If we can make one Julio-style opportunity clean and actionable, then we can scale it. If we cannot organize one, we should not pretend we can automate fifty.

Quick Legend

Strategy CardOne clean page for a messy ITB.
Protocol CaptureHow we learn your rules and preferences.
Recommendation ShelfSuggested plays for what to do next.
Response TimelineWhat happened, what changed, what is next.
Outcome ButtonsSimple call results that train the system.
Phase 0The paid proof sprint before larger automation.

Prototype only. Buttons show the intended workflow and do not send anything. Replace placeholder contacts with real ITB data before external use. All outbound messages remain approval-gated.