“Small businesses” is not a sufficiently precise audience for most business software. Companies in the same industry may approve quotations through email, a specialist system, or a process your product does not support. An industry label does not prove a pain point. A long feature introduction asks the recipient to discover the relevance for you.
Outreach supports public contact discovery, candidate review, email outreach, and communication history. This guide uses a hypothetical quotation-approval software vendor approaching industrial-parts distributors in Seoul. It is a workflow example, not evidence of customer adoption or a claim that any particular product has those capabilities.
Which workflow should you define first?
Define the task your product handles and separate facts from assumptions. The example concerns checking internal approval after a quotation is prepared. The vendor must still ask whether that work is repetitive and how the buyer currently handles it.
Describe the intended industry, supported geography and language, workflow, and exclusions. If your product does not replace accounting or inventory tools, make that explicit. Otherwise an early buyer may expect a much larger implementation than you offer.
Show only currently available functions and conditions. Do not promise unverified connections to other software or invented time and cost savings. Without a defensible customer story, explain the actual scope and ask a relevant question instead.
How do you search for businesses with a plausible fit?
Search for buyer categories where the workflow may occur, then qualify demand later. Local equivalents of “industrial parts distributor,” “tools wholesaler,” and “electrical supplies wholesaler” are candidate keywords. They do not demonstrate a confirmed software purchase intention.
Create a project and keyword groups with country, region, common words, and target. This example starts in Seoul. If your support model fits remote customers elsewhere, separate groups can cover other territories or countries. The project is not assumed to be limited to one country; your actual support conditions still matter.
Searching for “quotation approval software” alone may find competitors and product articles. Search for how the buyer describes its business. Review products and quotation enquiry routes on the website, while avoiding claims that you have discovered its internal tools.
Which contacts should you choose for the first approach?
Start with a route that can receive a business proposal. In the example, Email is Required, Phone is If available when calls are part of the plan, and Instagram handle is Skip. If you will not use the phone, skip that field too.
The current contact choices include Email, Phone, Instagram handle, and LinkedIn. The choices are Skip, If available, and Required. Every required field must exist. Missing optional information does not exclude a business satisfying the mandatory conditions. Requiring both phone and email excludes firms publishing only one. Skip means you do not purchase or receive that field.
Each received contact field costs one credit. A public company email is not guaranteed to be a personal address for the buyer or approval owner. Check whether a general inbox can route the proposal. Do not invent a person's name to make the message seem researched.
What can the results tell you about software fit?
They provide public evidence for a candidate, not proof of an internal problem. After selecting Start collecting, review Collection results and the company website. Does it supply industrial products to businesses? Does it handle quotation enquiries? Those observations can justify a question, not a diagnosis of its approval process.
Separate consumer-only retailers, unsupported industries, and companies outside your language or service conditions. Multiple branches do not automatically mean a complicated approval hierarchy. Keep current systems, permissions, and budget as questions for the conversation.
Download to Excel creates an Excel-compatible CSV, leaving unpurchased fields blank. Add separate columns for public evidence and unconfirmed hypotheses if a colleague will review the file.
How much product detail belongs in the first email?
Explain the current workflow scope and ask whether that workflow exists for the buyer. A question grounded in public relevance is more accurate than asserting an unverified problem. The example vendor asks about quotation approval and whether an explanation would be useful.
This hypothetical template must be adapted to a product whose functions you can verify. Include real sender information and the required recipient-country disclosures.
Subject: A question about quotation approval at {company_name}
Hello,
We provide business software for managing internal approval status after a quotation is prepared.
We are contacting industrial-parts suppliers about that workflow. Does your team currently check quotation approval across separate documents or messages?
If this work is relevant, may we explain the current screens and scope? This is not a proposal to replace inventory or accounting tools, and compatibility with existing software would need separate assessment.
Your real name, company, and contact details Please reply if you do not want further messages.
The message does not claim the recipient has a problem. It asks one question rather than demanding a meeting, trial signup, and purchase together. Invented enterprise clients or unsupported improvement figures would undermine that careful scope.
What should you inspect before sending?
Inspect the company name, product boundaries, and one clear response request. In Write your message, {company_name} in the subject or body is replaced with the company's name. Check Preview for natural wording and remnants of earlier campaigns.
Before sending, connect your own mailbox in Settings → Connect email and save your settings. Follow the provider-specific instructions shown there, then send a self-test to your own inbox. Use the account that will handle replies to this campaign.
Use Send yourself a test first to your own connected inbox. Confirm that demonstration links are suitable for external viewers and contain no private customer material. The first email should support one relevant workflow question, not reproduce an entire technical manual.
The test is not an ordinary prospect campaign and does not collect companies. Save first and follow-up messages separately, but review them when product conditions change. A saved paragraph may contain a capability you no longer offer.
What governs real sending and cost?
Review the sender, recipients, and contact requirements before starting the campaign. A public business email is not proof of marketing consent. Check consent, sender identification, and stop-contact requirements in the recipient country. KISA guidance and the FTC guide are starting points. An advertising label alone does not permit every message.
Email costs two credits per message. The basic gap is about ten minutes, is adjustable, and can vary. Immediate delivery and replies are not guaranteed. Consider the recipient's language and working hours rather than assuming the software settles those choices.
Respect stop requests in later campaigns too.
Which questions turn a reply into qualified discovery?
Ask about current work, users, and adoption constraints. Already sent and reply filters show communication history. Sent filters include recent seven, thirty, or ninety days and send count. A link click is an interaction with your material, not a product signup or paid adoption.
“We approve by email” confirms a current method. You still need to know who requests and approves, which record is required, and whether the product fits existing tools and permissions. “We would like an explanation” is not an implementation agreement.
Keep discovery, evaluation, actual signup, and paid contract distinct in your own records. Do not assume Outreach automatically retrieves registrations or payments from your software. Verify actual customer activity separately before counting it as an adoption result.
What should a software follow-up add?
Add verified information that helps assess fit. Filter already-sent companies without replies and manually use separate follow-up content where appropriate. For this example, explain what an approval requester and approver can actually see in the current product.
Silence is not proof that the buyer is wasting time or money. If its existing tool is sufficient, respect that answer. Stop on request, and review delivery failures before more contact; failed messages do not automatically retry.
For companies that reply, respond to their specific question instead of sending the same generic follow-up. If they ask about compatibility, describe only assessed conditions, not an untested promise of integration.
How do you begin with the free credits?
Start with one workflow hypothesis and one customer category. Signup includes one hundred free credits, with no monthly subscription. Receiving thirty email fields and sending thirty emails would hypothetically cost ninety credits. That arithmetic does not guarantee thirty customers, deliveries, or paid contracts. Additional received phone fields add cost.
Check the cost estimate and balance before collection. A project purpose such as “qualify quotation approval at industrial-parts distributors” keeps the search and question aligned. A smaller review can tell you whether the premise is useful before you broaden the audience.
Read the full service walkthrough and email writing examples, then sign up. Use Outreach to organise contacts and communication; assess product suitability and adoption through verified conversations and actual use records.
