The setting
offers , a platform where companies buy, set up and manage language-learning programs for their employees and get reports on how those programs are used.
Returning duplicate renewal payments risks undoing legitimate purchases.
Administrators want cash returned before their finance reviews, while finance wants to preserve cash through account credits.
Who you’d be doing this for
“Finance sent me two charges this morning. I've held the next department's rollout because I don't know what we're actually paying for.”
Farhad Kaya · Learning and Development Administrator · a character in this brief
Runs an employee language program at one of the companies that paused expansion after apparently repeated renewal charges.
What is at stake
Repeated renewal charges have put 74 companies' balances in doubt. You must weigh returning cash today against an irreversible refund of a legitimate purchase, without cutting off paid learners.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- cash returned to customers vs cash retained as credits
- refund certainty vs the submission cutoff
- financial correction vs uninterrupted learner access
- account isolation vs valid renewals continuing
Why Speak
Enterprise subscriptions connect company billing to learner entitlements, so a financial correction also puts employee access at stake.
Written with these in mind
Not your kind of problem? 41 more at Speak, 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 Speak. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Full-stack Engineer (opens in a new tab)
- You’ll set technical direction across the web acquisition and purchase journey, including public discovery, authentication, checkout, billing, provisioning, and measurement.
- You’ll work primarily in TypeScript across Next.js/React, Node.js, and Postgres, partnering with engineers in adjacent pods where the experience crosses team boundaries.
- Full-Stack Engineer - Enterprise (opens in a new tab)
- You’ll work across the B2B product surface — partner portals, reporting, B2B subscription mechanics, admin experiences, and learner features that require an enterprise touch.
- Near-term work includes B2B onboarding flows, partner-facing reporting, subscription and billing mechanics, and enterprise-ready features that support our growing Sales and CS motion.
- Engineering Manager, Enterprise (opens in a new tab)
- A strong technical background with hands-on experience in full-stack development and familiarity in our stack (TypeScript, React, Node.js, Postgres, BigQuery).
- Lead the engineering strategy and execution for the S4B roadmap, delivering features and infrastructure that serve our business clients.
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.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about money moving incorrectly, late, or twice.
Duplicate telemetry charges affect 2.3% of sampled usage as enterprise invoices approach close.
You must weigh a fast invoice correction against evidence strong enough to stand behind.
Some enterprise controllers are finding card policies attached to the wrong employee groups after setup changes.
You must weigh a reversible onboarding interruption against controls that may govern the wrong cards.
A billing agent proposed corrections across $3.2M in disputed invoice value, but its evidence is partly machine-summarized.
You must weigh faster customer relief against irreversible credits and month-end revenue exposure.
The same setting, from another role
Each is set around Speak’s Speak for Business, written for a different role. They’re separate briefs, not the same scenario.
Campaign evidence points in different directions, and Sales questions whether the leads are ready for enterprise conversations.
You must decide what AI can recommend, what strategists must judge, and how the team will trust the evidence.
Korea paid programs are drawing broad inquiries while L&D administrators need evidence for finance reviews.
You must decide what evidence-led motion to test without overstating what the program can prove.
Korea's remaining demand budget must produce 18 sales-accepted opportunities and ₩900 million in qualified pipeline this quarter.
You must weigh a faster event-led route against a paid channel playbook that could scale beyond Korea.
Other problems with a similar purpose
In each of these, as in this one, the aim is to build high-assurance systems where a consequential change's correctness can be demonstrated, not merely hoped for.
Rehearsals show the routing works, but recall of sources varies by 0.9% and provenance records are incomplete.
You have to weigh the contractual launch against how much you verify before each matter moves.
The old encrypted store retires on a fixed date, and 6.9% of historical artifacts still lack a source record and retention decision.
You have to weigh speed against proof that reports stay reproducible.
The residency commitment you signed forces a one-way split of event data, and 9% of derived datasets still lean on labels a machine guessed.
With six weeks left, you weigh completeness by region against keeping analytics intact.