Bringing AI in at Twilio

Draft proposals when discovery and buyer emails disagree

Published Oct 29, 2026

You’re a forward deployed engineer working with Twilio’s sales team. The team is in the room.

The setting

supplies cloud software that lets developers and businesses build messaging, voice, and email into their applications. Its gathers these tools, along with identity checks and customer data.

A complete-looking Messaging proposal can conceal an unsettled buyer assumption.

Sellers need a document buyers can act on, while Finance and Legal need its commercial departures to remain visible.

Who you’d be doing this for

“I moved our purchasing review again because the proposal used last month's country mix.”

Hugo Vega · Application Owner · a character in this brief

Coordinates a technology company's Messaging purchase and needs the proposal to secure internal approval.

What is at stake

Sellers found conflicting buyer assumptions in eight of twelve Messaging deals marked ready for proposals. You decide how a draft handles a country or volume figure when an Outreach email differs from the Salesforce record, and which differences go to the seller first.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • complete proposals vs explicit unknowns
  • latest correspondence vs confirmed discovery
  • customer-specific scope vs approved commercial language
  • broad deal coverage vs a bounded first deployment

Why Twilio

Messaging proposals join country and volume assumptions to usage-based pricing, making discovery interpretation part of the commercial commitment.

Written with these in mind

Workflow-focused forward deployed engineersSolutions engineers building customer-facing pilotsApplied AI engineers with integration experience

Not your kind of problem? 41 more at Twilio, or browse every organization.

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Twilio. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

  • Strategic Account Executive (opens in a new tab)
    • Create pricing proposals, negotiating terms and managing the contract process.
    • Opening doors to the purchase of Twilio’s products and services - including voice, messaging, email, contact centre, account security software.
  • Account Executive 4 (opens in a new tab)
    • Work with teams in Finance, Legal, Pricing, and Operations to design mutually beneficial contracts to address customer requirements, while balancing the needs of our business.
    • Work with customers across assigned verticals (Financial Services) to understand their business and technical requirements, and match them to the capabilities of Twilio’s communications API platform, designing a solution for their specific use cases.
  • Strategic Account Executive 5 (opens in a new tab)
    • Twilio powers real-time business communications and data solutions that help companies and developers worldwide build better applications and customer experiences.
  • Sales Development Representative 2 (opens in a new tab)
    • Growth-oriented and ready to build toward future leadership or customer-facing roles
    • Research accounts to determine how Twilio’s solutions can provide value, then execute outbound dials, personalized emails, and social selling.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these turns on committing to a deal before it checks out.

The same setting, from another role

Each is set around Twilio’s Twilio Customer Engagement Platform, written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to turn observed user friction into a fast, confident decision that visibly restores a better experience.