Meet the team that took the friction out of selling

Imagine having a signed deal, a ready customer, and a completed handoff — only to have your own system block you from closing it. For Smartsheet sales reps, this wasn't a hypothetical, it was a recurring reality that cost time, generated unnecessary administrative work, and for reps in Japan and Australia, regularly meant logging in at midnight to submit a deal that was already done.

Ryan Agnew, Nik Pettelle, Jonah Willis, and Emmett Worth set out to fix it. The result was the Future Dated Opportunity feature — and the story of how it got built is as much about how this team worked as what they shipped.

The problem was simple. The impact was not.

Before this feature existed, closing a future-dated deal meant a rep had to wait for the calendar to catch up with work that was already done. 

Ryan described the old experience: "A rep closes a deal on August 25th. Order form signed, customer ready, rep ready to move on. But the start date on the quote is August 29th. Rep submits the opp and gets a kickback: 'Start date is in the future.' They have to wait until August 29th to resubmit." If that date fell on a weekend, reps were logging in Saturday night to close a deal that was already finished.

For APJ-based reps, the stakes were higher. As Emmett noted, reps were regularly forced to wait until midnight PST to submit deals, creating delays for both them and their customers. Jonah added that minor errors compounded this further, triggering late-night interventions to correct and resubmit.

The data made the cost tangible: future-dated deals accounted for 16% of all internal order processing requests and 5% of all rejected deals — preventable friction that directly slowed sales.

From friction to alignment

The team first identified the issue during a Kaizen event in FY25, where a broader group mapped the full process from signed deal to active customer across deal types. That session surfaced clear deliverables, aligned stakeholders, and gave the core team organizational backing to execute.

Within the core team, what made the solution possible was the range of perspective each person brought. Ryan sat between the business and the floor — advocating for the sales experience while documenting and testing. Jonah owned the technical build: Salesforce logic, automation, and scalability. Emmett stress-tested assumptions and flagged downstream risks from a fulfillment lens. Nik held the structure: dependencies, timelines, scope, and the steady communication that kept everyone honest about what could realistically ship.

As Ryan put it: "We trusted each other enough to disagree on the right things, and align fast on what actually mattered." Jonah was direct: "No one person could have pulled this off alone."

Why the work was harder than it looked

The question was never whether to build the feature — it was how to build it correctly across every deal type in the system.

Future-dated new opportunities required different logic than expansions. True-ups had their own rules. Renewals couldn't change at all. Underneath all of it was significant technical debt, and there were moments when the original design didn't hold and the team had to pivot.

Nik recalled one early inflection point: "We hit a provisioning start date bug that could have caused billing issues. We had to fix that before launch, not after." Rather than push through, the team changed course.

What held the work together was operating rhythm. As Ryan put it: "Weekly alignment meetings became non-negotiable. Blockers, highlights, what's breaking, what's next. That rhythm kept us honest." The team was managing other large projects simultaneously, which meant every decision had to account for downstream impact. They moved slower and made sure it was right.

What changed after launch

The results came quickly and quietly.

The future-dated kickback was eliminated. No more Saturday night logins. No more waiting for a calendar to catch up with a deal already closed. For the APJ team, the response at launch was enthusiastic.

Jonah described the rep experience plainly: "To a rep, it looks like magic — click a button, fill in a few fields, and the customer gets the product exactly when expected." Behind that simplicity is a complex backend architecture. For Jonah, the real measure of success came after go-live: "Silence is the ultimate compliment. It means a process that could have been a buggy nightmare is running so smoothly it's invisible."

What this says about working here

The team didn't ship a workaround. They built the right thing, correctly, for every deal type — through unexpected bugs and mid-course pivots.

Nik reflected on what made it work beyond the output: "Everyone was genuinely driven, trusted each other, and delivered on their commitments. You don't always get that — real trust and chemistry. Honestly, it was fun."

That spirit carried into how they built: carefully, with an eye toward what comes next. As Emmett noted, "The foundational work was less flashy, but it set this and future projects up for success."

Wins like this happen because of the people behind them. If you're looking for a place where your work moves things forward, explore our open opportunities.