FY27 GTM Engineering
We're giving teams more AI tools, agents, and automation, so they can focus on the work that actually moves the business. The goal is to simplify and focus: fewer manual steps, fewer context switches, fewer things falling through the cracks.
Q3 Progress · Oct 5, 2026 · Cross-Functional Leadership
Q3 · Aug to Oct 2026 · Updated Oct 5
Four objectives, fourteen key results. Three complete and eleven still open in Wrike.
Complete In progress Past recorded due date · Wrike status checked Oct 5
The Agent Roster
Live agents, deployed workflows and the current build queue. Updated Oct 5.
CSM is moving from Databricks to AWS; its SuperOrgs tracking is broken. Sendo added live send and ship notice lookups on Oct 5.
Limited releases: Call Insights review app · Messaging Studio beta. Finance Command Center V1 delivered; broader project open.
Sente re-engagement and Marketplace tracking have live capabilities. AE launch remains on hold in Wrike. Lifecycle stage and release scope differ.
AM risk scans, stakeholder mapping and reviewed outreach · Onboarding handoffs · Marketplace tracking · Aged inventory campaign tools · Shared AWS runtime and customer intelligence access
Lifecycle scope: 17 roadmap agents. Seven new Q3 agents remains a separate target. SuperOrgs is used for lifecycle labels only, never ROI.
Sprint Delivery Roadmap
Delivery through October, then six remaining agents from the Wrike launch plan through January.
Q3 CLOSEOUT · OCTOBER
Playbooks · 4 of 10 recorded complete · remaining delivery and ownership targets due Oct 30Account intelligence · scoring complete · dashboard, Company Intelligence and signal actions still openOctober platform work · CSM AWS migration and tracking repair · onboarding scheduled cutover remains openQ4 sequencing is proposed; Wrike still targets Oct 30. AE needs a restart. Finance Agent is separate from the live finance dashboard.
Measurement & Value
Live tools are creating customer engagement, reducing manual work and replacing vendor spend.
| Launched work | What we can show today | What we measure next |
|---|---|---|
| Sendo ↗ | 20 people · 46 questions · 23 conversations Launch day report, Sep 30; agent reported. | Weekly active and returning users; resolved questions; sampled answer time and quality. |
| Sente ↗ | 2 meetings booked in 1.5 weeks Proactive re-engagement with meeting prep ready for the team. | Unique outreach → replies → held meetings → qualified opportunities. Deduplicate bookings. |
| Website Performance ↗ | Automatic daily refresh is live GA4 and Clarity reporting, Oct 1 release. | Report preparation time before and after; recurring users; completed analyses. |
| Support Console ↗ | Replaced Dataland ($42k) Support lookup workflows now run in our console. | Lookup time and success rate; ongoing operating cost and net savings. |
Completed tasks × observed minutes saved, after review and rework. Track hours before assigning dollar value.
Link held meetings and follow-up to CRM outcomes. Revenue attribution needs a baseline and comparable cohort.
Verified labor value + retired tool spend, less build and operating cost. Keep capacity value and cash savings separate.
Weekly review: usage logs, sampled task timings, CRM outcomes and Finance records. SuperOrgs ROI estimates are excluded; restore CSM tracking to measure its usage.
Show & Tell · ROI Reporting
Hours saved are the starting point. The stronger story is what got done, what grew revenue, and what costs came out.
01 · EFFICIENCY
Compare manual time with assisted time, including review and rework. Show capacity returned by workflow.
02 · EXECUTION
Count accepted Salesforce campaign setups, approved outreach and completed tasks. Track time to ready and quality.
03 · BUSINESS RESULTS
Connect activity to pipeline and Closed Won New ARR. Report sourced and influenced separately; keep expansion and retention distinct.
Request → configured campaign → validation → accepted Campaign ID
Report completed setups, median turnaround, first-pass acceptance and rework. Tie every result to a real record.
Sent outreach → Campaign Member → Sent / Responded
Replies and bookings feed the campaign. Next: distinguish held meetings, eligible opportunities and revenue. See workflow ↗
Proposed reporting model. Salesforce outreach tracking is live; portfolio-wide New ARR attribution and a general campaign setup report are next steps. Sente customer meetings are not counted as New ARR.
Show & Tell · Sendo Relaunch
Ask across conversations, support, account health, Salesforce and sends without assembling the context by hand.
01 · CUSTOMER CONTEXT
“Build a brief for [account]: recent conversations, support issues, health and renewal context. Show the sources.”
02 · LIVE SEND LOOKUP
“What is the current status of send [ID]? Include tracking, any recorded failure reason and data freshness.”
03 · REUSABLE OUTPUT
“Compare [account] spend in August and September. Explain the spend definition and export a CSV.”
Launch-day usage is from the reported recap. Demo prompts use a known account and valid send ID. Read and analyze access; bulk reports use refreshed warehouse data. Usage recap ↗
Show & Tell · Messaging Studio
A concrete, visual workflow for Sales and Marketing: context → draft → human review → export.
Use contact and account context. Choose cold outreach or account expansion, the outcome you want and a clear call to action.
Past performance and a winning library guide the draft. Review the copy, check evidence and approve before export.
Demo path: Compose → Drafts & review → existing fictional launch test → evidence → approved export.
Actual beta workspace · fictional demo sequence · captured Oct 5
Existing two-email demo inspected with an evidence reference and approved export. This workspace does not send messages. Adoption and reply-rate improvement remain to be measured.
Q3 Progress & Priorities
What has shipped, what remains open, and where October effort goes.
GTM Engineering: Building the "more" in "do more with more"
v2.9.2 · Oct 2026 · GTM Engineering
Q1 · Feb to Apr 2026
Two pulled to future state. Everything else shipped or rolled into Q2.
Proved Fivetran → Snowflake → Databricks architecture. New agents stand up in days, not weeks.
Account + Contact scoring deployed to AE team. Performance validated. Lead routing live April 3.
Visual lifecycle mapping with agent-consumable API. React Flow + Cloudflare. Auto-deployed.
Product data schema ready and updated in Databricks. AI and agent consumption ready.
Account, Contact, Opportunity objects documented at field level. AI/Databricks consumption ready.
End-to-end pipeline from agent idea intake through scoring, review, and sprint execution. Operational and repeatable.
Also shipped: Ticket Estimation System · Marketo Health Audit Workbook · Documentation Framework · Outbound Orchestration Consolidation · Sales Proposal Deck Automation
Q2 · May to Jul 2026
Four objectives, sixteen key results. Anchored to Simply Sendoso: Easier to See Value, Easier to Buy, Easier to Operate. Status as of Jul 26. 11 of 16 delivered.
Replace manual CX work with agents and automated value motions, measured by retention and expansion impact.
Better conversion, higher-quality pipeline. Supports $2.5M Q4 new ARR.
From reactive ticket-runners to autonomous execution.
Build the engine that ships AI safely at scale.
Archive
Context and framework slides kept in the v2.4.0 snapshot, plus concepts from earlier versions of this deck. Still relevant, just not in the main flow.
Claude is a tool people use. Agents are programs we build. Why decoupling the two matters.
The weighted scoring rubric and the intake-to-production pipeline behind every agent we build.
The framework, security, data layer, and structure that let a new agent stand up in hours.
Before/after/future stories for starter provisioning and Webflow self-service. The original "imagine a world where" framing.
Databricks One → Claude pockets → First Agents. Sequencing logic for the original rollout.
Three-tier autonomy framework: automated day one (internal), human-in-the-loop, graduated autonomous. Still the model we use.
All prior versions accessible via the Versions button (bottom-right).