Most SaaS marketing asks people to read about a problem. A free tool lets them solve a piece of it right now. That difference is why small utilities, graders, calculators, and generators keep showing up in the growth stories of software companies, and why the tactic has its own name: engineering as marketing.
This playbook covers where the idea comes from, how to choose a tool that actually feeds your product, how to build it so it earns trust instead of eroding it, and what to measure once it is live.
What engineering as marketing means
Gabriel Weinberg and Justin Mares list engineering as marketing as one of the 19 traction channels in their book Traction. The idea is to spend engineering time on useful things, such as free tools, calculators, and widgets, that put your company in front of potential customers. The tool is the marketing asset. Instead of a blog post that explains how to check your website, you ship the checker.
The canonical example is HubSpot's Website Grader. HubSpot says it launched the tool in February 2007 to generate traffic, inbound links, and leads for its marketing software. You entered a URL and got an inbound marketing score from 0 to 100 covering things like traffic, SEO, and social media. By HubSpot's own count it had graded 1 million URLs by June 2009 and passed 2 million about seven months later, and it spawned a family of other graders. The tool still exists today as a speed and SEO checker.
The pattern has not gone away. Ahrefs, for example, runs a page of free SEO tools, including a keyword generator and a backlink checker, each deliberately capped (the free backlink checker shows the top 20 backlinks) and each a short hop from its paid plans. The free version does a real job; the paid product does the bigger version of the same job.
Why free tools earn traffic, links, and signups
Free tools compound in a few ways that ordinary content struggles to match:
- They match tool-intent searches. People search for things like 'screenshot annotator', 'SOP template', or 'backlink checker' because they want to do something, not read about it. A page that does the thing is the most direct answer.
- They earn links without outreach. Teachers, bloggers, and forum answers link to tools far more readily than to product pages, because recommending a free utility costs the linker nothing.
- They get bookmarked and reused. A good tool is visited repeatedly, so your brand shows up every time someone does that recurring task.
- They qualify the visitor. Someone who just annotated a screenshot for a help article has told you, through behavior, that they write documentation.
None of this is automatic. A tool that is slow, ugly, or gated behind an email form gets none of these benefits, which is why the build decisions below matter more than the idea.
How to pick a tool adjacent to your product
The best free tools sit one step before or after your product's core job. Map the workflow your customers run, then look for a small task at either edge that people already search for and that you can solve completely in a browser.
- Write down your product's core job in one sentence. For a documentation product, it might be 'turn a workflow into a guide people can follow'.
- List the tasks right next to it. Before: capturing and cleaning up screenshots, outlining a procedure. After: annotating images for a help center, sharing steps with a teammate.
- Check demand for each task. Use your keyword tool of choice to see whether people search for that task by name, especially with words like generator, checker, template, converter, or calculator.
- Keep only tasks you can finish on the page. If the useful output requires an account, a server-side model, or your full product, it is a feature, not a free tool.
- Prefer tasks that recur. A tool used weekly builds more familiarity than one used once.
This is the logic behind Steperly's own free tools. Writing a guide usually involves screenshots, so the screenshot beautifier and screenshot annotator handle the image work in the browser, and the SOP template generator turns a simple form into a structured procedure. All three are free, need no sign-up, and sit right next to the core job of producing a step-by-step guide.
Honest tools vs. signup-wall landing pages
There is a cheap version of this tactic: publish a page titled 'Free X generator' whose only working element is a sign-up button. It can rank for a while, but it disappoints the exact people you want to impress, and it runs into search engine rules.
Google's spam policies define scaled content abuse as 'when many pages are generated for the primary purpose of manipulating search rankings and not helping users', and describe doorway abuse as pages created to rank for similar queries that funnel users to an intermediate page instead of what they came for. A run of near-identical 'free generator' pages that all lead to the same signup form fits that description uncomfortably well.
| Honest free tool | Signup-wall landing page | |
|---|---|---|
| What the visitor gets | A finished result on the page | A promise and a form |
| Account required | No (optional to save or go further) | Yes, before any value |
| Links it earns | Recommended in guides, forums, and answers | Rarely linked; nothing to recommend |
| Search risk | Low; it is the most useful answer | Looks like a doorway page at scale |
| What it teaches users about you | Your product probably works too | Your marketing over-promises |
There is a legitimate middle ground. If a capability genuinely needs your product, say so plainly: label it as a product page that starts on a free plan rather than calling it a free tool. On Steperly's tools page, browser tools and product-backed generators are labeled differently for exactly this reason.
Build it small, fast, and private
Free tools win on friction. A few build rules hold up across categories:
- Result above the fold. The input and the output should be visible without scrolling. Explanatory content goes below.
- Run in the browser when you can. Client-side processing is cheaper to host, faster for users, and lets you truthfully say files never leave the device, which matters for screenshots and documents.
- No account for the core job. Offer sign-up only for things that genuinely need it, such as saving history or doing the full-size version of the task.
- Export in the formats people use next. PNG for images, Markdown or Word-ready output for documents, a copy button for text.
- Write a real page around it. A short how-to, use cases, and FAQs help the page rank and help the visitor use it well.
The hand-off to your product should feel like the next step, not an ambush. After someone annotates a screenshot, it is reasonable to mention that the same arrows and step markers can be generated automatically from a recording. It is not reasonable to block the download until they create an account.
How to measure a free tool
Pageviews alone flatter free tools. Treat the tool like a product with its own funnel, and decide in advance what success looks like.
| Metric | What it tells you | How to track it |
|---|---|---|
| Completed uses | Whether the tool actually works for people | Fire an event on export, copy, or download |
| Returning users | Whether it became part of a routine | Repeat-visit rate on the tool page |
| Referring domains | Whether people recommend it | Backlink report for the tool URL |
| Assisted signups | Whether it feeds the product | Tag the tool as a touchpoint in signup attribution |
| Activation of those signups | Whether the audience is a fit | Compare activation of tool-assisted vs. other signups |
The last row is the one most teams skip. A tool can drive plenty of signups from people who will never use your product. If tool-assisted signups activate at a much lower rate than other channels, the tool is probably too far from your core job, and the fix is to choose a closer task rather than to add more gates.
Common mistakes
- Building something clever but unrelated. A fun tool with no connection to your product earns traffic you cannot convert.
- Gating the result. Asking for an email before showing the output trades long-term links and goodwill for a short list of reluctant leads.
- Launching once and forgetting it. Tools break as browsers and file formats change. Put them on the same maintenance list as your product.
- Mass-producing variants. Ten slightly different pages for the same tool look like a doorway pattern and split the links you earn.
- Hiding who built it. A clear brand and a short line about the full product is what turns usage into awareness.
A simple 30-day plan
- Week 1: Map the tasks adjacent to your core job and check search demand for each. Pick one.
- Week 2: Build the smallest version that completes the task in the browser, with a clean export.
- Week 3: Write the page around it: what it does, how to use it, use cases, FAQs, and one honest link to your product.
- Week 4: Instrument completed uses and assisted signups, share it where your audience already asks for help, and link it from your related blog posts and docs.
Then let it run for a quarter before judging it. Search rankings and links accumulate slowly, and the activation comparison needs enough signups to be meaningful. If it works, the second tool is easier, because you can link the two together and reuse the page template.
For more on turning product education into acquisition, see our playbooks on documentation-led growth and running a public changelog.