Default: Use $100K–<$5M as the first-pass range, then split into bands if lead quality suffers.
Answer / owner / next step:
Use this in the meeting
Start with the operating decisions, not the taxonomy weeds. Once John and Karen agree on value range, counties, stages, and no-go rules, the Dodge filter questions become simple yes/no calls instead of a hostage negotiation with checkboxes.
1. Meeting priorities: decisions we need first
These determine whether Dodge and the CRM become a clean bid engine or just another noisy inbox.
Now
Owner: John + Karen
10 questions
Default: Use the 44-county service-area list as the starting map; have Logan/Karen mark core vs stretch.
Answer / owner / next step:
Default: Leave SC out unless there is a specific strategic reason.
Answer / owner / next step:
Default: Run bid-now daily. Add early-stage relationship mining as a weekly search only if Logan wants it.
Answer / owner / next step:
Default: Both, but keep them in separate searches so Karen can see what kind of work is moving.
Answer / owner / next step:
Default: Build a named watchlist and use it for saved searches, CRM scoring, and alerts.
Answer / owner / next step:
Default: Use reject reasons from the first week to harden the saved searches.
Answer / owner / next step:
Default: Make no-go rules explicit before AI scoring writes anything into CRM.
Answer / owner / next step:
Default: Daily for hot bidding searches; weekly for relationship/watchlist searches.
Answer / owner / next step:
Default: Ignore ITB unless Andromeda sends downstream bid invites through Dodge.
Answer / owner / next step:
2. Dodge operating model + subscription/API
These questions protect the workflow from bad automation and Dodge-license weirdness.
Now
Owner: Karen + Dodge rep
10 questions
Default: Preserve Karen’s existing searches until she confirms what can be retired.
Answer / owner / next step:
Default: Document current plan, NC-only coverage, account owner, and Sharon/Dodge rep details.
Answer / owner / next step:
Default: Ask Dodge directly; do not assume a separate huge API fee or free access.
Answer / owner / next step:
Default: Prefer official API/feed. If unavailable, use official CSV export plus alerts.
Answer / owner / next step:
Default: Assume generic staging until Dodge confirms a supported Zoho path.
Answer / owner / next step:
Default: Use scheduled export if API is delayed; avoid browser automation unless Dodge grants written permission.
Answer / owner / next step:
Default: Verify field coverage before designing CRM fields.
Answer / owner / next step:
Default: Store raw payloads with retention metadata; clean up if license requires it.
Answer / owner / next step:
Default: Get the answer in writing before automating beyond human-reviewed exports.
Answer / owner / next step:
Default: Map the actual current behavior before replacing it.
Answer / owner / next step:
3. Geography, value bands, and project stages
The goal is fewer dumb leads, not more leads. This section turns Logan/Karen’s judgment into filter rules.
Now
Owner: John + Karen
6 questions
Default: Use two hours for normal jobs; allow stretch counties only for strategic/high-value jobs.
Answer / owner / next step:
Default: Core = daily Dodge searches. Stretch = monitor/search when scope is unusually strong.
Answer / owner / next step:
Default: Keep large/far counties separate so they don’t swamp eastern-NC fit.
Answer / owner / next step:
Default: Start with bands: $100K–$500K, $500K–$2M, $2M–<$5M, $5M+ monitor/strategic only.
Answer / owner / next step:
Default: Yes for daily action; Planning/Design can be weekly relationship mining.
Answer / owner / next step:
Default: Yes. Treat as GC/owner mapping and past-bid research, not daily bid queue.
Answer / owner / next step:
4. Dodge CSI division questions
Current selected CSI divisions are 02, 03, 05, 31, 32, 33, and 35. Ask these before widening the rule set.
Filter tuning
Owner: John + Karen
8 questions
Default: Leave unchecked unless Dodge uses it to surface GC/prime opportunities they actually want.
Answer / owner / next step:
Default: Leave unchecked for now; possibly relevant for marine/residential but likely broad.
Answer / owner / next step:
Default: Leave unchecked until confirmed.
Answer / owner / next step:
Default: Leave unchecked unless they actively want plumbing scopes.
Answer / owner / next step:
Default: Leave unchecked for now; 31/32/33 should catch most site-road work without DOT noise.
Answer / owner / next step:
Default: Leave unchecked unless industrial welding is a major growth lane.
Answer / owner / next step:
Default: Leave unchecked.
Answer / owner / next step:
Default: Leave unchecked unless confirmed.
Answer / owner / next step:
5. Dodge trade questions
Current selected trades bias toward civil/sitework, utilities, concrete, metals/welding, roadway access, and marine/coastal work.
Filter tuning
Owner: John + Karen
11 questions
Default: Leave unchecked unless they actively want excavation/dewatering leads.
Answer / owner / next step:
Default: Leave unchecked unless confirmed.
Answer / owner / next step:
Default: Leave unchecked unless confirmed.
Answer / owner / next step:
Default: Ask John. If dredging is a growth lane, add it.
Answer / owner / next step:
Default: Leave unchecked until Karen confirms how Dodge uses this label.
Answer / owner / next step:
Default: Leave unchecked unless they have a partner/self-perform path.
Answer / owner / next step:
Default: Leave unchecked to avoid hauler-only noise.
Answer / owner / next step:
Default: Leave unchecked unless fencing is a real pursuit area.
Answer / owner / next step:
Default: Add only if John/Karen say yes; it could be a useful sitework add.
Answer / owner / next step:
Default: Keep only if it yields civil stormwater jobs; remove if it pulls equipment vendors.
Answer / owner / next step:
Default: Keep if local/private/municipal roadway work is desired; remove if it floods the queue.
Answer / owner / next step:
6. Dodge project-type questions
Project Type should describe the job container Andromeda wants, not every scope they could theoretically touch.
Filter tuning
Owner: John + Karen
15 questions
Default: Leave unchecked unless they actively pursue bridge work.
Answer / owner / next step:
Default: Leave unchecked.
Answer / owner / next step:
Default: Leave unchecked.
Answer / owner / next step:
Default: Leave unchecked.
Answer / owner / next step:
Default: Leave unchecked for now; add only if Dodge returns useful park/sitework projects.
Answer / owner / next step:
Default: Leave unchecked to avoid landscape-contractor noise.
Answer / owner / next step:
Default: Leave unchecked until John/Karen confirm.
Answer / owner / next step:
Default: Leave unchecked unless treatment-plant civil/sitework is a real target.
Answer / owner / next step:
Default: Leave unchecked. Too easy to generate vendor/equipment noise.
Answer / owner / next step:
Default: Leave unchecked unless John specifically wants it.
Answer / owner / next step:
Default: Leave unchecked until confirmed; broad industrial gets noisy fast.
Answer / owner / next step:
Default: Leave unchecked. Website can credential broadly; Dodge should not become a vertical-building firehose.
Answer / owner / next step:
Default: Leave unchecked unless the queue is too narrow.
Answer / owner / next step:
Default: Leave unchecked.
Answer / owner / next step:
Default: Leave unchecked unless Karen says good projects often arrive uncoded.
Answer / owner / next step:
7. CRM / Zoho / Twenty pilot questions
The CRM should receive approved pursuits, not become a dumping ground for raw Dodge data.
Pilot design
Owner: Karen + JB
9 questions
Default: Human-approved only during the pilot.
Answer / owner / next step:
Default: Define authority now so the AI can route ambiguous projects correctly.
Answer / owner / next step:
Default: Keep Zoho for the first pilot. Revisit Twenty after one week of real Dodge intake.
Answer / owner / next step:
Default: Confirm before designing a Dodge_Project_ID upsert flow.
Answer / owner / next step:
Default: Use her working model first; normalize after observing real usage.
Answer / owner / next step:
Default: Title, county, value, bid date, stage, owner/GC, scope summary, documents, plan holders, score, next action.
Answer / owner / next step:
Default: Draft automatically for approved pursuits; require human approval before sending.
Answer / owner / next step:
Default: Top 5 + changes + urgent follow-ups. No giant daily PDF nobody reads.
Answer / owner / next step:
Default: Distance, wrong scope, too small, too large, bad owner/GC, bid date too soon, paperwork burden, missing docs/contact.
Answer / owner / next step:
8. Website / SOQ / public-facing fact confirmations
These only matter before demoing or publishing the Andromeda site/SOQ-derived copy. No invented numbers; SOQ wins.
Before publish
Owner: John + Karen
7 questions
Default: Use SOQ-confirmed contact info: John (919) 348-0414 and Karen (252) 558-6903 unless they prefer otherwise.
Answer / owner / next step:
Default: Lead with credential layer for bid/outreach workflows, not generic brochure traffic.
Answer / owner / next step:
Default: Remove unsupported claims until Logan/Karen provide exact language.
Answer / owner / next step:
Default: Use only SOQ-backed facts unless Karen provides corrected project sheets.
Answer / owner / next step:
Default: Use SOQ-confirmed leadership/personnel; avoid stale names.
Answer / owner / next step:
Default: Show enough to establish credibility, keep detailed compliance in downloadable packet.
Answer / owner / next step:
Default: Use direct CTAs unless a static-compatible form handler is intentionally wired.
Answer / owner / next step:
9. Optional: real-estate/development side thread
Not required for the Dodge demo, but useful if Logan steers the meeting toward property/development strategy.
Optional
Owner: John Logan
4 questions
Default: Keep separate unless Logan wants one shared relationship map.
Answer / owner / next step:
Default: Treat as separate strategic track; don’t mix with Dodge operations.
Answer / owner / next step:
Default: Keep legal/money-sensitive notes private until Logan explicitly approves storage/sharing.
Answer / owner / next step:
Default: Mark active vs context before building workflows around them.
Answer / owner / next step:
Sources consolidated
Generated from the local Logan workspace. Public/company claims still need SOQ backing before publishing; this artifact is for internal question collection.
docs/dodge-one-operations-playbook.md
docs/dodge-csi-division-questions.md
docs/dodge-trades-questions.md
docs/dodge-project-type-questions.md
docs/dodge-zoho-data-flow.md
docs/crm.md
docs/architecture.md
docs/andromeda-service-area-counties.md
docs/2026-04-25-project-review.md
docs/2026-04-24-day-analysis.md
docs/2026-04-25-am-limitless-extract.md