1Principles
Forms serve databases, not users.
- 8 WorkCharts built, zero accessible through conversation
- Every task requires: navigate module, find form, fill fields, wait
- Modality matrix: 49 transformations possible, 1 in use (text-to-text)
- Competitors shipping conversational CRM: HubSpot AI, Salesforce Einstein, Clay
| Problem | Question | Decision |
|---|---|---|
| 8 WorkCharts x 0 conversational entry | What if the agent were the interface? | Build chat-first, keep forms as fallback |
Picture
Sales rep at desk with 4 browser tabs open — pipeline, contacts, RFP form, email — trying to assemble context for a meeting in 10 minutes
2Performance
50% tasks via conversation.
| Metric | Target | Now |
|---|---|---|
| Tasks via conversation | >50% | 0% |
| Agent response time | <3s | N/A |
| Modality classification | >95% | N/A |
| RFP processing (PDF drop) | <5 minutes | N/A |
| Problem | Question | Decision |
|---|---|---|
| 0% conversational, 100% form-based | What makes a rep choose chat over forms? | First interaction must show CRM awareness |
Picture
Dashboard split — left: task completion chart with 0% conversational, right: target showing 50% conversational task completion
3Platform
WorkCharts built, wiring missing.
| Component | Built | Wired | Working |
|---|---|---|---|
| WorkChart orchestrators | Yes | Yes | Yes |
| Skill router | Yes | Yes | Yes |
| Vercel AI SDK | Yes | No | No |
| Chat UI | No | No | No |
| Modality router | No | No | No |
| Session memory | No | No | No |
| Problem | Question | Decision |
|---|---|---|
| Backend complete, frontend empty | What's the shortest path from user to WorkChart? | Wire useChat to skill router via streaming endpoint |
Picture
Architecture diagram showing 8 WorkChart boxes connected to a skill router, but no line from any user interface to the router
4Process
Text first, voice second.
| Tier | What | Effort | Unblocks |
|---|---|---|---|
| T0 | Text chat + session memory + flag | 5 days | Conversational access to all text-based WorkCharts |
| T1 | Modality router + WorkChart adapter | 5 days | Correct routing of any input to any WorkChart |
| T2 | File upload + streaming + rich results | 5 days | RFP processing via PDF drop |
| T3 | CRM queries + conversation history | 4 days | Pipeline visibility via natural language |
| T4 | Voice input (STT) | 3 days | Hands-free interaction |
| Problem | Question | Decision |
|---|---|---|
| Too many modalities at once | Which modality proves value fastest? | Text-only MVP, then file, then voice |
Picture
Build timeline showing T0 (text chat), T1 (modality router), T2 (file upload), T3 (CRM queries), T4 (voice) in sequence
5Players
Colleague, not chatbot.
| Job | Struggling Moment | Hidden Objection |
|---|---|---|
| Get answers fast | Navigating 4 modules to assemble context | "I'll spend more time explaining than clicking" |
| Process documents | Copy-pasting from PDF to form, losing formatting | "AI will miss context and I'll fix wrong answers" |
| Draft outreach | Context-switching between research and generation | "AI outreach is generic, I'll rewrite it anyway" |
| Problem | Question | Decision |
|---|---|---|
| AI skepticism from broken promises | How does the agent earn trust first? | First message must reference real CRM data, not generic |
Picture
Two screens side by side — left: generic chatbot saying 'How can I help?', right: agent saying 'Your Acme deal is stalling — want me to draft a follow-up?'
1 / 5