How We Closed a $70K Banking Deal (And What It Taught Us About Enterprise Sales)

The Deal That Changed How We Sell

It started as an inbound inquiry.

But it became something entirely different. A 6-month journey through compliance mazes, legal negotiations, incumbent lock-in traps, and ultimately, a midnight signature on December 31st, 2025, from a Bangkok hotel room.

This is the story of how we closed a $70K deal with a major FDIC-regulated financial institution. More importantly, it is what this deal taught us about selling to enterprise customers.

Why This Deal Mattered

Before diving in, you need to understand our sales structure.

At Signeasy, we are a lean team. That means one salesperson might handle a $4K SaaS deal while simultaneously managing a $50K API integration. The complexity, stakeholders, and timelines are completely different.

We needed two distinct sales processes:

• Sales Assist: High-velocity deals. Quick qualification, trial mode, no wasting time on unnecessary pricing discussions or proof cycles. Straight to close.
• Complex Deal: API-heavy, volume-based, high user count, multi-stakeholder, regulatory requirements. Needs a fundamentally different approach.

How We Define a Complex Deal (P1 Deal)

We classify a deal as P1 if it meets any of the following:

1. API-heavy, volume-based deals (regardless of company size)
2. SaaS platform deals over $10K on volume or number of users
3. Business-critical integrations that are central to customer operations

Why the special treatment?

• Operational criticality: These are not nice-to-have tools. For a bank using our API to issue loan documents, this is how they operate. Failure is not an option.
• IT-driven process: These deals require access to technical teams, security reviews, and legal sign-offs.
• Multi-stakeholder buying: Typically, IT stakeholders, CFO, and CEO are all involved, especially for greenfield projects or vendor replacements.

This banking deal was a textbook P1 deal.

Part 1: The Easy Part

July - August 2025: Discovery, POC, and Technical Win

Our banking customer came to us with a clear problem.

The Business Case at a Glance:

• FDIC-regulated financial institution, 100+ years in business
• Processing 20,000 loan documents per month
• Actually signing 12,000 to 13,000 per month
• Paying the incumbent vendor for all 20,000 documents
• Growing at 10% annually

Let that sink in: they were paying for 8,000 documents per month that never converted to actual loan signings.

The Cost Problem:

The incumbent's pay-per-send model charged for every document generated, signed or not. Documents abandoned mid-application? Still charged. At 100K+ documents annually, the waste multiplied.

Our Value Proposition Was Immediately Clear:

Pay only for documents that are actually signed, not documents sent.

$70K+ in savings over 3 years. A 35 to 40% cost reduction.

The Technical Win: Why They Had to Move Now

Current Setup:

• Embedded signing through their loan management system
• Supporting only 3 templates
• Limited ability to handle session restarts or API callbacks

What They Needed:

• APIs triggered when customers drop off mid-session
• Session restart support
• Flexibility for future product expansion

Their existing vendor contract renewal was coming in October, meaning they needed a 60+ day cutover window. They had to decide now, or stay locked in for another year.

The Champion: VP Digital

We started working with VP Digital, the person who owned the budget, felt the pain daily, and had everything to gain from solving this problem.

Who She Was:

• VP of Digital Division (reports directly to the President)
• Owned the e-signature platform budget
• Frustrated with the incumbent vendor's slow responses, misaligned pricing model, and minimal support during renewal negotiations

What Built Trust:

During the initial discovery and POC phase, we did something simple: we were responsive, and we built the business case together with her.

She specifically called out: "You guys were more understanding during the testing phase, and more responsive from the first email."

The POC: Early Technical Validation

We did not launch into a 90-day POC process. Instead, we moved fast.

What Happened:

• Initial technical exploration in July
• Engineers tested our API documentation
• Quick feedback loop: within hours, not days
• Clear go/no-go on feasibility

The Result:

• Engineering team confirmed: "Documentation is great, easy to test, no blockers"
• Technical risk was eliminated before commercial negotiations even started

End of Phase 1: Where We Stood

Momentum:

• Champion identified (VP Digital)
• Technical validation complete
• Business case proven ($70K savings over 3 years)
• Trust built through responsiveness

Open Questions:

• Who are all the stakeholders?
• What is the full buying process?
• How long will legal and compliance take?
• When can we actually sign?

We were confident. We were ready. We had no idea what was about to hit us.

Part 2: The Complications

August - November 2025: Executive Engagement, Legal, Compliance, and the Incumbent Curveball

The Executive Outreach That Changed Everything

We had a champion in VP Digital, but we knew we needed to connect at the executive level to move forward.

Our CEO reached out cold to the President of the Digital Division. No warm introduction. No mutual connection. Just a direct email.

She responded. And then our CEO flew to their office to meet in person.

This was bold. This was risky. But it worked.

Why This Mattered:

In enterprise sales, executive engagement signals commitment. When a vendor's CEO shows up, it says: "We are serious about this partnership." The President saw that commitment and it changed the trajectory of the deal.

Beyond building trust, the in-person meeting uncovered the full buying process. The decision did not end at the President level. It required board approval. And the board's first question was predictable: "We have never heard of this company."

We now knew exactly what we needed to prepare for.

Mapping the Organisation: Finding the Real Economic Buyers

This was not a simple approval chain. This was a multi-stakeholder sales cycle that went all the way to the board.

But understanding it upfront was our advantage. We were not blindsided in month four when the board suddenly needed sign-off.

Legal and Compliance: The Steepest Learning Curve

When you sell to a bank, legal and compliance are not add-ons. They are gatekeepers with veto power.

Without a dedicated internal legal team, the salesperson had to understand every concern, translate it to our product and legal teams, bring back answers, and repeat. More than 15 times.

The Key Concerns:

• Data security: How is customer PII stored? Who has access? What happens in a breach?
• Regulatory compliance: Does our platform meet applicable standards?
• Insurance: What is our coverage and liability?
• Service levels: What is our uptime SLA? What happens if we go down?
• Customer data ownership: Who owns the contracts processed through our system?
• AI features: Can they opt out of AI processing?
• Breach notification: How quickly do we notify them of an incident?
• Assignment rights: Can we sell the company without their approval?

What We Conceded:

• AI feature opt-out (no AI processing on loan documents)
• Customer data ownership (they own all contracts; we only process them)
• Notification timelines (changed from "immediately" to "reasonable time")
• Insurance requirements (negotiated coverage amounts)

What We Held Firm On:

• Assignment rights (we can assign on change of control, merger, or to affiliates)
• Service level commitments (provided historical uptime data, not hard SLAs)
• Data use language (we can use data to maintain and support services, with opt-outs available)

The Silence: When Everything Paused

With legal and compliance negotiations underway, things went quiet. There were still occasional check-ins, but momentum felt off.

What Was Happening Behind the Scenes:

• Legal and compliance teams were in full negotiation mode
• The board briefing process was moving more slowly than expected
• Internal stakeholders across different departments had different concerns

Our Response:

We had two choices: push harder and demand timelines, or trust the relationship and give them space. We chose the latter.

Our CEO put it simply: "Let us look at this long-term instead of just meeting our quarterly goals."

Breaking the Silence: The Board Presentation

Our CEO followed up directly with the President. The response revealed what was actually happening: the President needed to present Signeasy to the board before any contract could move forward.

With help from our marketing team, we built a comprehensive deck to address every board-level concern:

• Vendor stability: 15 years in market, 10M+ users, 150+ countries
• Cost savings: Quantified $70K+ savings over 3 years
• Technical fit: Engineering validation results
• Risk mitigation: Phased implementation approach
• Regulatory compliance: SOC 2 certification, uptime data, insurance coverage

VP Digital and the President presented this to the board. We then got on a call together to walk through questions.

And that is when the real curveball arrived.

The Incumbent Lock-In: What the Board Call Revealed

On that same call, a critical detail surfaced that changed the entire deal structure.

We cannot exit the incumbent early. We needed to give 74 days notice, and we missed that deadline.

What This Meant:

• The incumbent contract extended into 2026
• They could not immediately switch off the old system
• Options: pay an early-termination penalty, or negotiate envelope credits

They went back to the incumbent and secured 9 months of envelope credits. Instead of paying a termination fee, they received 9 months of continued usage on the old system. This meant they could begin integrating Signeasy without paying for two platforms simultaneously during the transition.

Impact on the Deal:

• Go-live had to be delayed until incumbent credits were consumed
• Implementation timeline shifted significantly
• Payment structure needed a complete rethink
• Q4 2025 deployment was no longer possible

But the board had seen the deck. They understood the value. Walking away was not on the table.

Part 3: The Hardest Part

November - December 2025: Re-Scoping, Final Negotiations, and the Midnight Signature

Re-Scoping the Deal: Making It Work

With the incumbent lock-in confirmed, we had to completely restructure how the deal was priced and phased.

Original Plan: Sign in Q3, implement in Q3/Q4, go live October 2025

New Reality:

• Transition could not begin until Q2 2026
• Signeasy implementation could not start until Q2 2026
• First live loan documents would not flow through Signeasy until Q3 2026

The Problem: How do you charge for a platform no one is using for 6 months?

The Solution:

• Lock in pricing now (December 2025)
• Customer pays an implementation fee upfront
• Usage-based billing starts when they actually go live (Q3 2026)
• Billing tied to envelope credits transferred from the incumbent (50% of credits by end of Q2 2026)

The Revised Timeline

The Moment: December 31st, 2025, 10 PM, Bangkok

Throughout this entire 6-month process, VP Digital had never once picked up the phone. Every update, every decision, every question came through Slack and email.

On December 31st, we sent over a revised order form. It was 10 PM in Bangkok.

And then the phone rang.

It was VP Digital.

She had questions. We talked through the final details. And by the end of that call, the order form was signed.

No fanfare. No video conference. Just a late-night phone call that broke six months of email-only communication, and closed the deal.

$70K in value locked in. Deal done.

Learnings That Stuck

Learning 1: The Real Pain Is Not What They Tell You

Here is what customers say when you ask why they want to switch vendors:

• "We need to reduce costs"
• "The platform is missing features"
• "Looking for better support"

None of these are the real pain.

The real pain: every month, our banking customer paid for 8,000 documents that did not turn into revenue. That was real, quantifiable, and visible in the P&L.

Learning 2: Speed Is a Competitive Advantage

When asked what the deciding factor was in choosing to work with us on the POC, VP Digital's answer was simple: "Your response time."

Not our features. Not our pricing. Not even our product.

We responded to emails within hours. We showed up ready to problem-solve. We did not make her wait.

Learning 3: Courage Is Underrated

Cold outreach to the President of the Digital Division was bold. No warm introduction. Just: here is the problem you have, here is how we solve it, let us talk.

And then showing up in person.

Most vendors send an email. Some send a follow-up. Our CEO showed up at their office.

Learning 4: It Takes a Village

This deal involved the entire organisation:

• Sales: Discovery, champion identification, deal management
• Product and Engineering: Technical validation, POC, API support
• Marketing: Built the board presentation deck
• Legal: Negotiated contract terms, managed compliance
• CEO: Executive relationship-building and credibility
• CS and Implementation: Committed to the delivery timeline

Learning 5: You Have to Speak Legal Language

Legal concepts like limitations of liability, indemnification, breach notification, and opt-out clauses directly affect deal terms. If you do not understand what you are agreeing to, you might lock yourself into impossible commitments.

Learning 6: Long-Term Mindset Changes Everything

When we shifted from "close by Q3" to "build a long-term partnership," everything changed. We could accommodate timeline delays. We could focus on their success, not our quota. We could negotiate in good faith.

What This Means for Your Sales Process

The Framework: Two Distinct Processes

Process 1: Sales Assist (Simple Deals)

• Quick evaluation (1 to 2 weeks)
• Single stakeholder
• Standard terms
• Fast to implement

Process 2: Complex Deal (P1 Deals)

• Extended discovery (4+ weeks)
• Multiple stakeholders
• Custom terms, longer implementation
• Requires executive engagement, legal review, and compliance sign-off

The Checklist: Is This a P1 Deal?

Answer YES to 3 or more of the following, and treat it like a P1 deal:

• Is this API-heavy and volume-based?
• Is it mission-critical to how the customer operates?
• Does it require IT and technical team involvement?
• Does it need legal and compliance review?
• Is the deal size above $10K for SaaS or above $50K for API?
• Will multiple stakeholders need to approve?
• Is there regulatory complexity (FDIC, HIPAA, SOC 2)?

P1 deals require more sales time upfront, product and technical team involvement early, a 4 to 6 month sales cycle minimum, executive engagement for credibility, preparation for legal negotiation, and custom deal structures.