The setting
's is cloud-based software that manages hiring pipelines and workflows for startups and growth-stage companies that are scaling their hiring.
A complete proposal can make an unresolved assumption look like an agreed term.
Sellers need a coherent commercial offer, while implementation reviewers need uncertainty about responsibilities to stay visible.
Who you’d be doing this for
“Finance asked whether the implementation work was included. I had to book another call because the proposal didn't say who was doing it.”
Sari Aung · Head of Talent · a character in this brief
Evaluating a replacement for several recruiting tools and preparing the proposal for finance review.
What is at stake
Five of 12 replacement deals leave cost assumptions unresolved in discovery. You decide whether AI drafts those proposal lines with explicit gaps or leaves them for sellers to write before approval.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- complete proposals vs visible unknowns
- buyer-specific language vs approved commercial wording
- structured deal fields vs nuance in discovery
- early commercial clarity vs unresolved implementation scope
Why Ashby
Replacing several recruiting tools puts pricing, consolidation scope, and implementation responsibilities into the same buyer conversation.
Written with these in mind
Not your kind of problem? 15 more at Ashby, 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 Ashby. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Sales Manager, Mid-Market - EMEA (opens in a new tab)
- Sales Leader, Enterprise - Americas (opens in a new tab)
- Manage deal risks and help navigate the complexities of large-scale competitive replacement deals.
- Enterprise Account Executive - Americas (West) (opens in a new tab)
- Mid Market Account Executive - Americas (West) (opens in a new tab)
- You will help us win Mid-Market accounts in the Pacific and Central time zones by managing the full sales cycle from pipeline generation through to closed-won.
- Mid Market Account Executive - EMEA (French Speaking) (opens in a new tab)
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 betting growth on an outside partner or launch.
Enterprise buyers still cannot tell which demonstrated capabilities their paid evaluation includes.
You decide whether AI may draft scope from demo evidence or must obtain a seller’s explicit selection before that scope enters the proposal.
Five of eight payer deals contain requests beyond approved proposal language.
You decide whether AI drafts those requests as marked terms or leaves them as questions for the seller.
Proposal reviews are starting with missing qualification evidence and conflicting accounts of the buyer’s process.
You have to decide where a drafted Salesforce field stops being a note from a call record and becomes a seller's claim about what the buyer committed to.
The same setting, from another role
Each is set around Ashby’s ATS (Applicant Tracking System), written for a different role. They’re separate briefs, not the same scenario.
Recruiters are manually copying assistant-generated candidate updates, leaving hiring reviews with conflicting pipeline records.
You have to weigh faster recruiter flow against a candidate record that leaders can trust.
Contractor recruiters can sign in but cannot open requisitions or schedule interviews before a five-day cutover.
You must weigh uninterrupted hiring access against permission boundaries that cannot be casually reopened.
Duplicate HCM requests are creating parallel requisitions and dividing candidate activity between them.
You must weigh retry resilience against a clean recruiting record that recruiters can trust.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make the background systems nobody sees behave dependably even under heavy, high-volume real-world load.
Eleven of the 18 committed workflows still need manual follow-up to provision accounts or hand over equipment, and hiring dates are fixed.
You have to weigh a faster launch against the risk of wrong access or a dropped handoff.
Deal managers are opening dozens of document views to infer which reviewers are engaged.
You have to weigh a faster deal signal against permission-safe visibility.
Incorrect confirmations are sending patients into clinic callbacks and invalid appointment slots.
You have to weigh rapid restoration against the proof needed before changing a live scheduling workflow.
