TuckerAI Platform

project 0ba5edb3f946f05f
Normalized: tuckerai platform
moreland_contracts
44%
Separation Confidence How distinct this entity is from others. Higher means no close matches existed when it was created. Lower means a near-match was rejected just below the 80% threshold — worth reviewing.
Moderate — a somewhat similar entity exists
100%
Avg Match Confidence The average confidence score across all active source mappings. Shows overall quality of linkage between source records and this canonical entity.
Strong source linkage

Source Mappings (1)

Source Source ID Display Name Confidence Method Status Actions
moreland_contracts a771d22032ba8e74d8a208d308bd9416 TuckerAI Platform 1.00 fuzzy+embedding Active
Source Record bronze_moreland_contracts_ma_project_contracts
file_hash
a771d22032ba8e74d8a208d308bd9416
file_name
TuckerAI_Phase1_Roadmap_Client_2026-07-30.docx
file_path
https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7BEB01EA32-FDDB-4FFF-A652-A3DF2D271389%7D&file=TuckerAI_Phase1_Roadmap_Client_2026-07-30.docx&action=default&mobileredirect=true
company
1st American Courier
project_name
TuckerAI Platform
contact_person
David Holtkamp
contract_type
time_and_materials
hourly_rate
estimated_hours
1015.0
total_fee_estimate
brief_project_description
Scope, effort sizing, and delivery timeline for Phase 1 (MVP) to retire Logitrack and CXT.
start_date
extracted_at
2026-09-02T02:06:15.292927+00:00
raw_text_preview
FEATURE COMPLETION ROADMAP — PHASE 1 TuckerAI Platform — 1st American Courier Scope, effort sizing, and delivery timeline for Phase 1 (MVP) — what's needed to retire Logitrack and CXT — reflecting the July 28, 2026 discovery call with David Holtkamp (1st American Courier) covering MVP scope, authentication direction, and tech-stack decisions. Roadmap at a Glance The table below sizes every Phase 1 (MVP) item using relative effort tiers (XS–L, and XL for the single largest build) alongside today's build status and what's changing about each. A full delivery timeline follows in the next section so you can see scope and schedule together. MVP Total estimated effort — Phase 1 (MVP): roughly 900–1,130 hours for a 3-developer team MVP Timeline Illustrative sequencing for the Phase 1 (MVP) scope above, built on the AI-agent-accelerated estimate for a 3-developer team at 80% effective capacity (accounting for meetings, code review, PTO, and other non-project time). At this capacity the timeline spans ~19 weeks (~4.5 months). Week numbers are planning placeholders — swap in real calendar dates once work begins. Testing follows an agile delivery model rather than a traditional waterfall hand-off. Each feature's bar on the following page ends in a hatched tail representing that item's own built-in QA/testing time — roughly the last fifth of its duration — already factored into its effort sizing, not layered on top as extra work. The practical effect: every feature ships tested as it's completed, rather than queuing behind one late-stage regression pass that traditionally creates a testing bottleneck right before launch. Reading the Timeline Each task's duration reflects its relative effort size (XS–XL) from the roadmap above, divided across the team at 80% effective capacity — not an independent guess. If an item's scope changes, its bar here should move with it. Billing (AR) is the critical path — the longest pole in the schedule (XL-sized, ~10 weeks), since the rate-card
file_created_at
2026-08-27T15:46:59+00:00
file_modified_at
2026-08-27T15:46:58+00:00
created_by
Paul Franke
modified_by
Paul Franke
_dlt_meta