Cold LinkedIn Outreach Before You Build: Uplane’s Learn-First Route

Uplane’s early acquisition story starts with strangers, not a finished product. In SaaS Club’s account, co-founder Julius Körfgen says he contacted people on LinkedIn to learn about their work, used discovery calls to uncover problems, and returned with working solutions built alongside his co-founders. He also reports selling to early customers before writing code. For an aspiring software founder, the useful idea is not simply “sell first.” It is to make customer conversations answer linked questions: Is this problem worth paying to solve, and can you deliver the solution economically?^[1]

Keep the headline outcome separate from the method. The episode reports that Uplane reached $1 million ARR in about six months, but the supplied evidence contains no revenue records, customer-side confirmation, or breakdown of revenue attributable to LinkedIn. It also leaves the recurring-revenue definition and software-versus-services contribution unspecified. Even the sales chronology is incomplete: the account describes both selling before code and building demos after discovery, without documenting contract or payment timing. Treat this as a founder-reported acquisition case, not a verified funnel or a revenue forecast.^[1]

Choose a narrow audience and make an honest request

Start by deciding whose workflow you want to understand. Uplane’s earliest prospect-selection process is not documented, so there is no source-backed list of roles or companies to copy. Separately, outreach vendor Waalaxy recommends defining an audience by factors such as sector, position, company size, maturity, and geography. Use that as supplemental targeting advice, not evidence of Uplane’s practice. Promtly’s recommendation: choose a recognizable workflow within a narrow customer group, then record why each prospect might know it firsthand. That gives you a reason to contact them beyond their job title.^[1][2]

Körfgen says his outreach introduced him as a founder who had left his job, explained that he was exploring an idea in the recipient’s field, and asked permission to ask questions rather than immediately requesting a meeting. No verbatim message is supplied. Here is a Promtly adaptation, not his script: “Hi [name]—I’m exploring software for [specific workflow]. Your role at [company] looks relevant, and I’m trying to understand how teams handle [task] before deciding what to build. Would you be open to a few questions here?” Use only details that are true, including your stage of development.^[1]

The important boundary is honesty, not a particular wording trick. Waalaxy recommends concise, authentic messages; Körfgen describes a humble, grateful tone. Neither establishes that calling something “research” makes outreach effective. If you are exploring a commercial product, say so. Do not promise a research exchange and then spring a demo on someone who agreed to answer questions. Promtly’s suggested progression is to begin in the format the recipient accepts, then ask whether a call would help clarify the workflow. A refusal should remain a refusal, not an invitation to change channels and keep pressing.^[1][2]

Turn discovery into a specific buying decision

Körfgen describes discovery calls in which he only asked questions. The sources provide no transcript, so the following is Promtly’s proposed interview structure: ask the prospect to walk through a recent instance of the task, explain the current workaround, identify where work stalls, and describe the consequences. Then ask who owns the problem and who could authorize spending. Prefer concrete examples to reactions to your proposed features. A useful call should leave you with a task, an obstacle, and a buying path—not merely an encouraging opinion about your idea.^[1]

Before proposing a build, reflect the problem back and ask the prospect to correct your interpretation. Then explicitly change gears: would they consider paying for a narrowly scoped solution if it met an agreed condition? This is a recommended bridge between learning and selling, not a documented Uplane script. Körfgen says he refused free pilots because payment distinguishes a business case from a polite conversation. That is a useful challenge to vague enthusiasm, but the account does not establish that refusing every free pilot is universally better. Nor does it disclose Uplane’s initial prices or pilot terms.^[1]

Make the commercial test concrete before committing substantial work. Promtly recommends writing down the deliverable, exclusions, required customer inputs, acceptance condition, price, and when payment becomes due. Ask the prospect to confirm those terms rather than merely agreeing that a solution sounds useful. Keep verbal interest, agreement to terms, and money received distinct in your notes. Uplane’s reported story does not reveal whether its early commitments involved deposits, signed contracts, or later payment. You therefore cannot copy its transaction mechanics, but you can avoid leaving your own ambiguous.^[1]

Copy the short feedback cycle, not the delivery promise

Körfgen says he ended discovery calls by promising to return in one week with a solution, which he and his co-founders would build and demonstrate. That deadline is not automatically transferable to a solo founder. Uplane’s official page identifies Julius Korfgen, Lukas Vollmer, and Marvin Abdel-Massih as its co-founders and describes CTO Vollmer as having fifteen years of product-building experience. The episode supplies no engineering-hour totals, scope boundaries, or failed-sprint history. Copy the short distance between understanding a problem and testing a working response; choose your deadline from your actual capacity.^[1][3]

A practical adaptation is to isolate the smallest useful task you can demonstrate with the customer’s inputs. Agree on what the demonstration must show, identify dependencies before starting, and disclose any manual work behind the result. Do not imply that a limited implementation is a complete product. Uplane’s current official demo offer promises real branded ads and landing pages within days, which supports the company’s stated emphasis on tangible output. It does not independently validate the early delivery story or establish that a new solo founder can match that turnaround.^[1][3]

The economic risk is accumulating unrelated customer projects instead of reusable software. This is a risk to examine, not a documented Uplane failure. For each proposed build, identify what could serve another customer and what exists only for this engagement. Include your delivery and support time when judging whether the price works. Körfgen describes Uplane’s pricing as a cost-covering fixed fee plus a variable share of ad spend, but its early margins are undisclosed. That pricing model is not a ready-made answer for your business, and a fee tied to spending is not itself proof of improved customer outcomes.^[1]

Measure movement toward payment, not just replies

The episode gives an approximately 5% response rate for Körfgen’s outreach. That is not a booked-call rate or a customer-conversion rate. The sample size, measurement period, denominator, and split between positive and negative replies are absent. There is also no reliable basis here for estimating acquisition cost or prescribing outreach volume. The sources do not establish whether Uplane used manual messages, automation, or InMail, and provide no LinkedIn policy guidance. Use the response figure as a limited anecdote, not a benchmark that determines whether your attempt is succeeding.^[1]

Instead, maintain a simple prospect log that separates messages sent, replies, substantive problem discussions, agreed commercial terms, payments, delivery, and continued use. This is Promtly’s recommended measurement system; those conversion stages are not quantified in the Uplane account. Record objections and reasons conversations stop. If people reply but describe no consequential problem, reconsider targeting or the problem hypothesis. If they acknowledge pain but will not discuss spending, investigate ownership and urgency. If paid interest requires work you cannot deliver economically, narrow the offer before sending more messages.^[1]

Keep your build schedule separate from the buyer’s decision schedule. Alongside the one-week delivery account, Körfgen describes a Deutsche Bahn project getting underway after roughly nine months of conversations. Fast implementation does not establish fast purchasing. At the end of each substantive exchange, ask what must happen next, who needs to participate, and whether the prospect wants further contact. Keep building contingent on a credible commercial step rather than an indefinite expression of interest. For your next outreach attempt, prepare the audience hypothesis, honest message, discovery questions, and delivery boundaries before opening LinkedIn.^[1]