"Our current process works fine"
Likelihood: ★★★★★ | You'll hear this on almost every call
"It probably does work - the question is what it costs you. Can I ask: how many hours per week does your team spend on invoice data entry?"
They're not saying "no" - they're saying "I don't see the problem." Your job is to help them quantify the hidden cost of "fine."
- "How many invoices do you process per month?"
- "How long does each one take to enter?"
- "When was the last duplicate payment?"
- "How often do you miss early pay discounts?"
"So 500 invoices × 10 minutes each = 83 hours/month. At $25/hour fully loaded, that's $25K/year just on data entry. Does that sound about right?"
"Totally fair. What would need to change for this to become a priority?"
This tells you the real blocker.
"Not right now" / "Maybe next quarter"
Likelihood: ★★★★★ | Classic stall, happens constantly
"Totally understand. What's happening next quarter that would make it a better time?"
Forces them to articulate the real reason. Often there isn't one - it's just a polite brush-off. Or they'll reveal the actual blocker.
"Makes sense. Can we do a quick pilot now so you have data for budget season? No commitment - just see the output quality."
"What's the bigger priority right now?"
(Then tie your solution to that priority if possible)
"I get it. What if I send a 2-minute video showing exactly what this does, and you can watch it when you have time?"
"No problem. When you're entering invoices manually next month, think about whether that time could be better spent. I'll follow up in [X weeks]."
"Just Exploring" / "Gathering Information"
Common Variant- "We're just gathering information"
- "No timeline yet"
- "Just seeing what's out there"
"Got it - what triggered the exploration now?"
Surfaces the real motivation. Even "just exploring" has a trigger - something made them search, take the call, or respond to outreach. Finding that trigger reveals the actual pain point.
"What would need to be true for this to move from exploration to action?"
If they say "no specific reason" - probably not a real prospect. They either have no budget authority, no timeline, or were just curious. Qualify harder or move on.
"Never heard of you" / "You're too small"
Likelihood: ★★★★☆ | Very common for early-stage startups
"Fair point - we're newer. That's actually why we're so focused on making each customer successful. You're not ticket #50,000 to us."
- "We're early, which means you get direct access to the team building this."
- "Our tech is built on the same AI infrastructure the big players use."
- "We're priced for growing companies, not enterprise budgets."
"The big players charge $50K+ and take 6 months to implement. We can have you live in a week. Which matters more - brand name or actually solving the problem?"
- "Start with 10 invoices. See the output before you commit to anything."
- "Month-to-month, cancel anytime. No long contracts."
- "I'll give you my cell - you can text me if anything breaks."
"We're early, so I can't drop big logos yet. But I can show you exactly what the output looks like on YOUR documents. That's more relevant than a case study from a different industry anyway."
"Too expensive" / "No budget"
Likelihood: ★★★★☆ | Common, but often not the real objection
"Too expensive compared to what?" or "Help me understand - is it the monthly cost, or is there no budget allocated for this at all?"
"I hear you. Let's do the math: if you're processing 500 invoices/month and each takes 10 minutes, that's 83 hours. At $25/hour, you're spending $2K/month on data entry alone. We cost less than that and give you the time back."
- "When does your budget cycle reset?"
- "Is there a smaller scope we could start with?"
- "What would you need to see to make the case internally?"
"Manual is never free - it costs you hours every week. The question is whether those hours are worth more than what we charge."
- "Let's start with the smallest tier. Upgrade when you see the value."
- "I can do [X]% off the first 3 months while you prove the ROI internally."
- "What number would work for your budget?" (Then see if you can meet it)
"I need to talk to my boss"
Likelihood: ★★★★☆ | Classic end-of-call move
"Of course. What questions do you think they'll have?"
You're helping them prepare, but also surfacing the real objections.
"Want me to send you a one-pager you can forward? Or I'm happy to join a quick call with them - sometimes it's easier than playing telephone."
"When are you talking to them? Can we schedule a follow-up for right after so I can answer any questions that come up?"
"Hey, what did [boss] think? Any questions I can help with?"
Sometimes "I need to talk to my boss" means "I'm not interested." If they won't schedule a follow-up or give you the boss's contact, it's probably a soft no.
"Will this work with our ERP/accounting system?"
Likelihood: ★★★☆☆ | Common from technical or IT-involved buyers
"What system are you using?"
DO NOT claim specific integrations without verifying with engineering first. We currently have NO native integrations with NetSuite, SAP, QuickBooks, or any ERP systems.
- CSV/Excel Export: Download structured data and import into any system
- Webhook API: Push data to your systems when invoices are processed
- REST API: Pull data programmatically for custom integrations
"We don't have native integrations with most ERPs yet. What we do have is CSV/Excel export and a webhook API. Most customers start with export-to-CSV because it's zero IT involvement - takes 30 seconds to import. Does your system accept CSV imports?"
"We can push data via webhook when invoices are processed. Does your system accept inbound data via API? If so, our dev team can help you set that up."
"Which integration would you need to move forward? Let me check with our team on timeline - but I want to be upfront that native integrations aren't on our immediate roadmap."
"How do I know this actually saves time?"
Likelihood: ★★★☆☆ | Skeptical buyers, especially if burned before
"Fair question. Let's test it: upload 5 invoices right now and see how long it takes vs. entering them manually."
"I can tell you it saves 80% of time, but that's just a number. Let me show you what the output looks like on your actual documents."
"You said you do 400 invoices/month at 10 min each. That's 67 hours. If we cut that to 2 minutes of review each, that's 13 hours. You get 54 hours back. What's that worth?"
"What happened with the last tool you tried?"
(Listen. Then explain how you're different.)
"We're looking at other options"
Likelihood: ★★☆☆☆ | Less common early, more common later in pipeline
"Smart to compare. Who else are you looking at?"
- vs. Big players (ABBYY, Kofax): "They're great if you have $50K and 6 months. We're built for teams that want to move fast."
- vs. Cheap OCR tools: "Those extract text. We extract structured data AND validate it against your POs. Different problem."
- vs. Building in-house: "Totally doable if you have the dev time. Most teams find it's cheaper to buy than build."
"[Competitor] is solid. The main difference is [specific thing you do better]. Depends what matters most to you."
"Happy to wait while you evaluate. Just know our pricing goes up next month / we're limiting new customers / [real reason to act soon]."
Competitive Positioning
Know Your Opponents"Tipalti is great for enterprise - 196 countries, global payments. They're also $50K+ and 6-month implementations. We're built for companies that want 80% of the functionality at 20% of the cost, live in a week."
"Bill.com is solid for basic AP. Where we're different: we handle complex invoice formats, PO matching, and document types they can't touch."
"ABBYY is the gold standard for enterprise OCR - they're in the Gartner Magic Quadrant. But they're priced for Fortune 500. We use similar AI technology at a fraction of the cost."
When We're NOT the Right Fit
Be Honest- Global payments needed: If they need to pay vendors in 100+ countries with local compliance, Tipalti is probably the right answer
- Multi-entity consolidation: Fortune 500 with dozens of subsidiaries and complex intercompany accounting - point them to Coupa or SAP
- Fortune 500 scale: If they're processing 100K+ invoices/month with a dedicated AP team of 50+, enterprise solutions make more sense
Better to disqualify early than waste everyone's time. A referral to the right solution builds trust for future opportunities.
"This sounds like a lot of work to set up"
Likelihood: ★★☆☆☆ | Change management anxiety
"It's actually really simple - no IT needed. You email invoices to your inbox or upload them. That's it."
- "Sign up - 2 minutes"
- "Get your email address for forwarding invoices"
- "Start sending documents"
- "Data shows up in dashboard"
"There's no implementation project. No integration required to start. You can be processing invoices in 10 minutes."
"You don't have to change your process. Just add one step: forward invoices to us before you enter them. We'll have the data ready when you need it."
Realistic Timeline
Set Expectations- Sign up and verify email
- Upload first batch of PDFs
- See extracted data in dashboard
This is the "10 minutes" claim - direct upload only, no integrations.
- Set up forwarding rules in their email client (Outlook, Gmail, etc.)
- Test that forwarding actually works (sometimes blocked by IT)
- Verify documents arrive correctly and process
- May need IT help depending on company email policies
- Review extracted fields and adjust settings
- Test with real documents from their actual vendors
- Set up any export or integration preferences
- Train whoever will be using the dashboard daily
Change Management
Reduce Risk"Start with one document type - invoices only. Get that working smoothly before adding POs, receipts, or anything else. Master one thing first."
"For the first week, run parallel with your current process. Enter invoices both ways. You'll see exactly how much time you're saving - and if anything goes wrong, you haven't dropped the ball."
"Who on your team is going to own this? Pick one person to be the expert - they learn it, they troubleshoot it, they train others. Don't try to train everyone at once."
Common First-Week Questions
FAQ"Our AI learns from patterns. If a vendor uses an unusual format, it may take a few invoices before it picks up on it. Flag it in the dashboard and we'll prioritize improving accuracy for that vendor."
"Check if the email forwarding is actually working - sometimes IT rules block auto-forwards silently. Or try uploading directly while we troubleshoot the email path."
"Yes - anything you upload during testing can be archived or deleted. We won't count test documents against any usage limits."
"Export all your data anytime - it's yours. No lock-in, no penalties. We want you to stay because it's working, not because you're trapped."
"Our dev team can build this"
Likelihood: ★★★☆☆ | Common from tech-forward companies
"Totally doable if you have the dev time. Let me ask: how long would it take to build, and what else would that team NOT be building during that time?"
You're not challenging their technical ability - you're reframing this as a resource allocation decision. Every engineering hour has an opportunity cost. Your job is to make that cost visible.
- Maintenance burden - OCR accuracy degrades, vendors change invoice formats, edge cases multiply. Who fixes it at 2am?
- Knowledge concentration - The dev who builds it becomes a single point of failure. What happens when they leave?
- Opportunity cost - Every sprint on internal tooling is a sprint NOT spent on your core product
- No SLA - When it breaks, there's no support ticket. It goes to the bottom of the backlog
"Your devs cost $150K+/year fully loaded. If this takes 3 months of one engineer, that's $40K+ before maintenance. We're a fraction of that - and you get updates, support, and your dev back on revenue-generating work."
Sometimes building in-house IS the right call. Acknowledge it:
- Massive scale - Processing millions of documents where per-unit cost dominates
- Unique requirements - Highly specialized document types no vendor handles
- In-house AI team - You already have ML engineers with spare capacity
"If you're at true enterprise scale or have very specialized documents, building might make sense long-term. But even then, most companies start with a vendor to learn what they actually need before committing engineering resources."
Don't trash their engineering team or imply they can't build it. They probably can - that's not the point. The point is whether they SHOULD. Saying "you can't build this" will make them want to prove you wrong.
"We can't forward emails to a third party"
Email forwarding, data privacy, and security concerns
Email Forwarding Objection
Most Common- "Our IT policy doesn't allow forwarding emails externally"
- "Those invoices have sensitive vendor/pricing data"
- "We can't send financial documents to a third party"
- "Email forwarding is a security risk"
"I understand - email forwarding can feel risky. Here's what actually happens: you forward to a dedicated inbox that only you can access. It's encrypted in transit via TLS, we extract the PDF, process it, and the structured data appears in your dashboard. It's actually more controlled than invoices bouncing between 5 people's inboxes with no tracking."
"Data security should be non-negotiable - I completely agree. Can you help me understand what specific concerns your team has? We may already address them, and if not, I want to understand what we'd need to demonstrate."
"Right now, where do those invoices go? Emailed to AP, forwarded to a manager for approval, CC'd to accounting, maybe saved to a shared drive... How many copies exist across how many inboxes? Our intake is one controlled channel with an audit trail vs. documents scattered everywhere."
"If email forwarding is a hard no from IT, you can upload directly - drag and drop PDFs into the dashboard. Same processing, no email involved."
What We Actually Have (Be Honest)
- Row-Level Security (RLS) enforced at the database level
- Even if our code had a bug, the database itself prevents cross-customer access
- Every query automatically filtered to your company - no developer can forget a WHERE clause
- Even our database superuser can't bypass these policies
"Your data is isolated at the database level using Row-Level Security. Even if a developer made a mistake in code, the database itself prevents any cross-customer access. It's not just access control - it's architectural isolation."
- Documents stored in AWS S3 (same infrastructure banks use)
- AWS-managed encryption at rest (AES-256)
- TLS encryption for all data in transit
- Presigned URLs - documents go directly to S3, never through our servers
- We use xAI's Grok model for document parsing
- We don't train any models on your documents
- Documents go in → structured data comes out → nothing retained for training
- All LLM calls logged with cost tracking
"We don't train on your data. We use xAI's Grok model to extract the information, and that's it. Your invoice goes in, structured data comes out, nothing is retained for model training."
- Delete your account → all S3 documents physically removed
- Database records soft-deleted (immediately inaccessible)
- Password verification required for deletion
- Audit trail of deletion (IP, timestamp)
- API key authentication with rate limiting
- No "browse all customer files" interface exists
- CORS whitelist - only approved domains can make requests
- Security headers (HSTS, CSP, XSS protection)
If They Ask About Compliance
"We're not SOC 2 certified yet - we're an early-stage company. But our architecture follows SOC 2 principles: database-level isolation, encryption, parameterized queries, rate limiting, soft deletes. We run on AWS infrastructure which is SOC 2, ISO 27001, and FedRAMP certified. Happy to share technical details with your security team."
"We're a funded startup with good security foundations, not an enterprise vendor with a compliance team. If you need HIPAA, SOC 2, or customer-managed encryption keys today, we're probably not the right fit yet. But if you want solid security at a price that makes sense for a growing company, we've got you covered."
Discovery Questions
- "Walk me through what happens when an invoice arrives today?"
- "How many people touch it before it's entered into your system?"
- "How many copies of that invoice exist across email, shared drives, desktops?"
- "If you needed to find an invoice from 6 months ago, how long would that take?"
- "What's your current process for deleting vendor data if they request it?"
(These questions reveal the chaos - multiple copies, no audit trail, manual handoffs, no deletion process)
Reduce Risk / Comfort Offers
"Happy to start with a few old invoices - nothing current or sensitive. See the output quality before you commit to anything real."
"If you want, I can share our security documentation with your IT team before you upload anything. Let them vet us first."
- "We're SOC 2 compliant" - we're not certified
- "Military-grade encryption" - meaningless marketing term
- "Bank-level security" - vague and oversold
- "No one can ever access your data" - we have infrastructure access for maintenance
- "End-to-end encrypted" - misleading; AWS manages the encryption keys
- "100% secure" or "unhackable" - legally risky, nothing is 100%
- "We have comprehensive audit logs" - we log deletions, not all access
If they require SOC 2, HIPAA, customer-managed encryption keys, or on-premise deployment - be honest that we can't meet those requirements today. Better to disqualify early than waste time on a deal that won't close.
General Principles
Core guidelines for handling any objection
Never Argue
Don't say "but..." or "actually..." - agree and redirect. "You're right, AND here's another way to look at it..."
Ask Questions
Every objection is a chance to learn what they actually care about.
Get Specific
Vague objections ("it's expensive") need specifics ("compared to what?")
Reduce Risk
Pilot, trial, month-to-month, money-back - make it easy to say yes.
Know When to Walk
If they won't engage after handling objections, they're not a fit right now. Thank them, stay friendly, follow up in 3 months.
MEDDIC Qualification Checklist
FrameworkMetrics
"What specific numbers will improve?" - Tie the solution to quantifiable outcomes they care about.
Economic Buyer
"Who signs off on purchases like this?" - Identify the person with budget authority.
Decision Criteria
"What's most important when you evaluate options?" - Understand their priorities.
Decision Process
"Walk me through how you've purchased software before" - Map the buying journey.
Identify Pain
"On a scale of 1-10, how urgent is solving this?" - Gauge if the pain is acute enough to act.
Champion
"Would you be comfortable advocating for this internally?" - Find your internal sponsor.
Champion Building
Your internal advocate is the difference between a deal and a dead lead
Why Champions Matter
35% faster sales cycles - champions remove friction you can't see
A champion sells when you're not in the room. They answer objections, push through procurement, and keep the deal alive.
Champion vs Coach
- Has authority - can influence the decision or is the decision maker
- Has personal stake - their job gets easier, they look good, they solve their problem
- Will advocate - actively pushes for you internally, not just friendly
- Gives you access - introduces you to other stakeholders
- Friendly and helpful, but no real influence
- Gives you information but can't push deals forward
- Says "I like it" but not "I'll fight for it"
- Refers you to others but doesn't advocate
"If I asked you to present this to your CFO next week, would you be comfortable doing that?" A coach says "probably." A champion says "yes, let me set that up."
Champion Signals
- Asks implementation questions - "How would we handle X scenario?" "What does onboarding look like?"
- Uses "we" language - "When we implement this..." vs "If you sold this to us..."
- Shares personal stake - "I spend 10 hours a week on this" "This would make my life so much easier"
- Volunteers internal info - tells you about budget cycles, who to avoid, what happened with the last vendor
- Proactively follows up - emails you back fast, schedules the next meeting without chasing
- Defends you to others - "I talked to my boss about this and here's what she said..."
- "This looks interesting, send me more info"
- "I'll share this with the team" (but never does)
- Answers your questions but never asks their own
- Always available for calls but nothing moves forward
Multithreading Questions
Use these to expand beyond your single contact and build multiple relationships in the account.
"Who else needs to be comfortable with this for it to move forward?"
"Who else on your team deals with this pain day-to-day?"
"When decisions like this get made, who typically weighs in?"
"Is there anyone who might push back on this that we should address early?"
If your champion leaves, gets busy, or loses influence, your deal dies. Multiple contacts = deal insurance.
When Your Champion Goes Dark
"Hey [Name], just checking in - any updates on your end? Happy to help if anything's come up."
"Thought of you - saw this article on [relevant topic]. Curious if you're still dealing with [their pain point]?"
"[Name], I want to be respectful of your time. Is this still a priority, or has something changed? Either answer is fine - just want to know where we stand."
"Hi [Other Contact], I've been working with [Champion] on invoice automation but haven't been able to reach them. Is this still something your team is exploring?"
Move to nurture list. Set a reminder for 3 months. Don't burn the bridge - priorities change, and they may come back.
Red Flags
Signs they're probably not a fit right now - and what to do about it
Low Intent / No Urgency
Ask: "What would need to happen for this to become a priority?" If they can't answer, add to nurture list and follow up in 3-6 months.
Counter: "Happy to - but materials alone don't capture it. Can we do 10 minutes next week so I can walk you through the most relevant parts?" If no, nurture list.
Try to create urgency: "Most teams see ROI within 30 days. What if we did a quick pilot and you had data before your next budget cycle?" If that doesn't land, nurture list.
Being Used for Leverage
Call it out gently: "Totally fair to compare. What would we need to show you to actually switch, not just negotiate?" If they can't articulate a real reason to switch, don't invest heavy time. Stay friendly, follow up in 6 months when their contract renews.
Champion Problems
If you multithreaded: reach out to other contacts immediately. If not: find out who took over their responsibilities and start relationship-building from scratch. The deal timeline just reset.
Process Blockers
After 2 reschedules: "I know you're busy. Is this still something you want to explore, or should I check back in a few months when things calm down?" Give them an easy out. If they take it, nurture list.
Ask: "What's the typical timeline for legal review?" If it's longer than your deal cycle can support, be honest: "We might not be the right fit right now. Happy to revisit when you have a faster path." Don't waste months on a deal that won't close.
Bad Fit Signals
Politely disqualify: "To be honest, at that volume you might not see enough ROI to justify even our lowest tier. If volume grows, definitely reach back out." Don't force bad-fit customers.
Offer to wait: "That's a big project. Let's reconnect in 3 months once you're settled in the new system - we'll integrate much more smoothly then." Set the follow-up now.
Dig in: "What happened with the last tool?" Listen carefully. If their issues were accuracy, explain how you're different. If they just didn't want to change, this probably isn't the right time. Nurture list, check back in 6 months.
Buyer Personas
Complete strategy for each persona - triggers, discovery, math, hooks
Accounts Payable
- Hiring AP roles - growth signal, capacity constraint
- ERP migration - integration window opening
- Acquisition/funding - new vendors, scaling
- New CFO/Controller - change agent in place
"I saw you posted an AP specialist role. Is invoice volume outpacing your current process?"
"I noticed your company just acquired XYZ. That usually means a lot of new vendor invoices coming through."
- "How many invoices does your team process monthly?"
- "How long does each one take to enter?"
- "When's the last time a duplicate payment slipped through? What did it cost?"
- "Are you capturing your early payment discounts?"
Duplicates: 2% rate × 500 invoices × $5K avg = $50K/year
Early Pay: 60% of invoices × 1.5% discount = $45K/year
Month-end: 2 extra days × 5 people × $50/hr = $4K/close
Procurement
- Hiring procurement roles - team expansion
- Acquisition activity - new vendors, supplier consolidation
- Facility expansion - new warehouse, distribution center
- Vendor consolidation - active rationalization initiatives
"I saw the new warehouse expansion. With that many new suppliers coming on, you'll have a lot more vendor emails hitting AP."
"Noticed you just brought on 50 new vendors after the acquisition. That usually means a wave of new invoice formats."
- "What percentage of invoices come in without a PO?"
- "How do you track vendor compliance?"
- "How many suppliers do you currently manage?"
- "When you have supplier issues, how do you handle them?"
- PO to Invoice to Receipt matching - catches discrepancies before payment
- Vendor consolidation - merge duplicate vendors, standardize master data
- Full traceability - every field traces back to source document
Controller / CFO
- New CFO/Controller - wants quick wins, visibility
- Audit prep underway - surfaces invoice matching issues
- Funding round closed - new vendors, complexity
- SOX compliance deadline - control gaps exposed
"I saw you brought on a new CFO. CFOs usually want visibility into duplicate payment leakage immediately."
"I noticed your audit prep is underway. That usually surfaces invoice matching issues."
- "When's the last time a duplicate invoice slipped through?"
- "Are you capturing your early payment discounts?"
- "How much time do you spend on month-end reconciliation?"
- "What's your current cost per invoice processed?"
Early pay discounts: 2% × $5M spend = $100K uncaptured/year
Cost per invoice: 500 × 12 min @ $50/hr = $5K/month
Fraud risk: $50K-$500K per incident (industry avg)
Operations / Warehouse
- New distribution center - wave of new supplier onboarding
- Regional expansion - more warehouse operations to coordinate
- Peak season prep - receiving efficiency matters more
"I saw you announced a new distribution center opening. That usually means a wave of new supplier onboarding."
- "How do you know what's arriving before the truck shows up?"
- "How often do you catch shortages at the dock vs after stocking?"
- "When shipments don't match POs, how do you handle it?"
Ops is an influencer, not budget holder. May champion cross-functional tools but needs finance sign-off.
IT / ERP Admin
- ERP migration announcement - integration challenges surface
- New system implementation - more integration work
- Hiring IT roles - team is stretched
"I saw your ERP migration announcement. ERP migrations usually surface integration challenges we can help solve."
- "How much time does your team spend maintaining AP integrations?"
- "When vendors change invoice formats, who handles that?"
- "How often do you deal with ERP sync failures related to vendor data?"
IT is gatekeeper for technical requirements, NOT budget holder. Lead with "zero IT involvement to start" - they like tools that don't add to their workload.