Enterprise Sales With No Product: Landing a Big Four Customer

概览

This episode features Christian Lund, co-founder of Templafy, an enterprise document automation company serving large organizations. The conversation traces how Templafy was spun out after the cloud shift, starting with two founders, two engineers, and no finished product, then growing into an eight-figure ARR business with around 200 employees.

The core discussion is about selling enterprise software before the product is mature. Lund explains how Templafy used domain expertise, thought leadership, and highly targeted messaging to win early enterprise conversations, including a global Big Four accounting firm customer.

A major theme is sales discipline: Templafy avoided small, vague pilots by saying “yes, if” and requiring clear buying intent, budget, timeline, success criteria, and a path to broad rollout. The episode later connects those lessons to AI, where Lund says Templafy again had to rethink its technology foundation, but initially communicated too far ahead of customer readiness.

分段落总结

[00:37] Episode Introduction

[事实] Omer Khan introduces the show as a SaaS founder interview podcast focused on how companies are actually built.

[事实] The guest is Christian Lund, co-founder of Templafy, which the intro says now does eight figures in ARR with a couple hundred employees.

[事实] The episode promises to cover selling before having software to show, handling small pilot requests from large customers, prospect disqualification, and an AI messaging mistake.

[01:40] What Templafy Does

[事实] Christian describes Templafy as an enterprise-focused document automation product.

[事实] The product helps employees across large organizations reduce the work involved in creating business documents.

[事实] Christian says the company has around 200 employees and an eight-figure revenue level.

[02:23] Why Templafy Was Spun Out

[事实] Before Templafy, the founders ran Omnidocs, which solved a similar document-related problem with an older technology model.

[事实] The cloud shift around 2012-2014 changed how businesses bought and expected to use technology.

[事实] The founders decided they needed to rebuild from the ground up to match where enterprise customers were going technologically.

[推测] The decision was less about finding a totally new customer problem and more about rebuilding the delivery model around a major platform shift.

[04:25] Starting Again From Omnidocs

[事实] At the time, there were five partners in the original business.

[事实] One technical co-founder spent about a year learning cloud technology and effectively unlearning the old approach.

[事实] Christian and co-founder Henrik took Templafy forward, while the other partners continued running the existing business.

[事实] Templafy began with the two founders and two engineers working from scratch.

[06:10] Selling Thought Leadership Before Product

[事实] Christian says large enterprises during major technology shifts were often buying people who understood the transition, not just finished products.

[事实] Templafy’s early sales were based heavily on thought leadership, domain knowledge, and explaining how document creation would change in a cloud world.

[事实] One of the first customers was a Big Four accounting firm on a global deal.

[事实] Templafy wanted to co-create with such customers so the eventual product would be grounded in demanding enterprise use cases.

[08:01] Getting Into Enterprise Conversations

[事实] Christian says Templafy used an unfair advantage from Omnidocs, including existing access to enterprise contacts.

[事实] The company was deliberate about targeting a specific message to a specific group of people.

[事实] Christian estimates they identified roughly 800 people worldwide who were mature enough in their thinking and relevant enough in their roles.

[事实] Templafy also raised its first funding round close to 12 months before having a product.

[推测] Early credibility came from combining existing relationships with a clear narrative about the future, rather than relying on a standard product-led demo motion.

[11:17] Building V1 Without Becoming a Custom Shop

[事实] Christian says Templafy wanted to learn from enterprise prospects while still trusting its own domain knowledge.

[事实] The team tried to avoid simply building what customers asked for, comparing that risk to the “faster horse” problem.

[事实] Templafy showed customers what the founders believed they needed, then iterated as the product matured.

[推测] This reflects a founder-led product strategy where customer discovery informed the direction but did not fully dictate it.

[13:45] Every Enterprise Customer as Its Own Market

[事实] Christian says the first unnamed Big Four customer was part of a broader accounting and consulting customer base.

[事实] Templafy pushed for company-wide adoption from the beginning rather than starting with a small team.

[事实] Christian argues that enterprise security and approval processes can be similarly heavy whether the rollout is for 10 people or 100,000 people.

[事实] The company aimed to land broadly across an organization, then expand into deeper and more specific team-level use cases.

[推测] The “customer as its own market” idea means a single large enterprise can contain enough internal teams, workflows, and document types to support major expansion after the initial deal.

[16:46] Avoiding the Small POC Trap

[事实] Christian says many large prospects asked to start with a 10-person proof of concept.

[事实] Templafy saw vague small pilots as risky because they could consume startup resources without leading to real deals.

[事实] The company required clear timing, budget, buying intent, rollout expectations, and proof criteria before agreeing to a POC.

[事实] If those prerequisites were not in place, Templafy would walk away.

[19:24] The “Yes, If” Response

[事实] Christian says Templafy did not simply say no to POCs; it said “yes, if.”

[事实] The team would agree to a POC only if both sides defined what was being proven and what would happen afterward.

[事实] Christian distinguishes between a POC to see whether a customer likes something and a POC to prove whether it works.

[事实] By defining success criteria early, Templafy often shaped the criteria later used in tender processes.

[21:12] Defining Proof and Next Steps

[事实] Christian gives examples of proof criteria: accessing the right templates, providing required inputs, seeing whether an add-in appears, and checking whether populated information is correct.

[事实] Templafy tried to make the criteria concrete enough that both sides could agree whether the proof had succeeded.

[事实] After successful proof, Templafy pushed for the widest possible rollout.

[事实] The company then used broad adoption to go deeper into specific teams and use cases.

[24:31] The First Enterprise POC Was Difficult

[事实] Christian says the first major enterprise implementation was unbelievably difficult.

[事实] He says early enterprise startups often need to look bigger than they are.

[事实] Templafy put as many people as possible onto the project because the opportunity was too important to fail.

[事实] The customer experienced delays and questioned why things were taking longer than expected.

[事实] Christian says the process produced a strong reference customer and made the product about 70% better.

[26:45] Transitioning Away From Pure Thought Leadership

[事实] Christian says companies cannot keep reinventing the wheel through thought leadership conversations forever.

[事实] Once Templafy had a product, it moved toward stronger prospect disqualification.

[事实] The company focused on prospects already open to the change Templafy believed was happening.

[事实] Christian says he does not believe sales is about convincing people.

[推测] Templafy’s sales philosophy depended on finding prospects whose worldview already matched the market shift, rather than trying to convert skeptics one by one.

[31:22] AI as a Second Technology Reset

[事实] Christian compares the AI shift to the earlier cloud shift.

[事实] He says some competitors previously tried to make older products “cloud-ish,” while Templafy rebuilt from scratch.

[事实] Templafy has taken a similar approach with AI, rethinking the technology foundation rather than merely adding AI features.

[事实] Christian says AI in enterprises needs guardrails and should act more like a controllable coworker than an all-powerful tool.

[事实] He says Templafy has spent the past two and a half years redoing the product from a technology perspective.

[34:47] The AI Messaging Mistake

[事实] Christian says Templafy’s big AI mistake was communicating too far ahead of the market too early.

[事实] He says being 15% ahead can work, but being 80% ahead can lose people in the conversation.

[事实] Early customers were more focused on how AI could help individual employees immediately.

[事实] Templafy was talking more about how enterprises could reclaim control over AI as it became central to business operations.

[事实] Christian says this caused Templafy to be disqualified in some conversations and opened the door for competitors with simpler messaging.

[36:26] Current AI-Era Challenges

[事实] Christian says a key challenge is differentiating at the right pace.

[事实] He believes Templafy can use its enterprise foundation to apply AI to document workflows in a differentiated way.

[事实] He describes mature companies as optimized for “downhill skiers,” meaning people who execute repeatable processes efficiently.

[事实] During disruption, he says companies need more “uphill skiers,” meaning people willing to find new paths and operate with startup-like uncertainty.

[推测] The hardest internal challenge is not only product strategy, but resetting the organization’s operating mode after it has already matured.

[40:53] Lightning Round

[事实] Christian’s business advice is that “best practice is worst case,” meaning a company should start from the best known standard and build beyond it.

[事实] He recommends Lucky Per/A Fortunate Man, describing it as a Danish classic about entrepreneurship and the personality traits behind it.

[事实] He says the best money spent on the business was investing in people and building a tight early team culture.

[事实] For personal productivity, he says he is using AI heavily, especially Claude and Gemini.

[事实] Outside work, he names family as his most important passion.

播客点评/总结

[推测] The episode is most useful for B2B SaaS founders selling into large enterprises, especially those dealing with long sales cycles, proof-of-concept requests, and market-category education.

[推测] Its strongest practical insight is the “yes, if” approach to pilots: it gives founders a way to engage serious enterprise buyers without being trapped in open-ended trials.

[推测] The discussion is less tactical on exact sales scripts, pricing, or implementation details, but it is strong on strategic judgment: when to lead customers, when to disqualify them, and how to handle a technology platform shift.

[推测] The AI section is valuable because it shows that even a mature SaaS company can mistime its narrative. The lesson is that being right about the future is not enough if customers are not yet ready to buy that version of the future.