How to market your product as a technical founder

You can build anything, but when you put your product online, almost nobody came. To market your product as a technical founder, you do not need a new skill first. You need to move your hours: marketing first every day, code after, and features only when people who fit ask for them. If you go back to coding, the pattern repeats: build, post, a few likes, then nothing.

Do these three things

About 5 to 6 hours of marketing a day, every day, and at most 2 hours of code. Judge it after 2,800 messages, about 4 weeks.

Show the three actions in fullHide the full list

1. 1Today: stop adding features. Block the first 5 hours of every day for marketing, before you open your code editor, and move every feature idea to a request sheet.
2. 2Every day: send 100 personal messagessoon to people who have the problem your product fixes, and ask for a 15-minute chat, not a sale. AI drafts each one; you add one true line about the person.
3. 3Every Sunday: count signups by where they came fromsoon and move your hours to what worked. Build only the features that 3 or more people who fit asked for.

Get help doing these

ChatGPT or Claude reads this guide and works through it with you.

Do this with ChatGPT(opens in a new tab)Do this with Claude(opens in a new tab)

1. Stop adding features and put marketing first in your day#

Block the first 5 hours of every day for marketing, and code for at most 2 hours after it. Until you have users who ask for things, another feature does not bring anyone to your product.

Building got cheap. In the first 3 months of 2026, new app releases on Apple's and Google's app stores were up 60% on a year before (Appfigures data), as AI coding tools took off. More features no longer set you apart. People knowing your product exists does.

Do this today:

1. 1

   Block your marketing hours

   In Google Calendar, make a block for the first 5 hours of your working day, set to repeat every day. Put a 2-hour code block after it. If you have a day job, put the marketing block first in the hours you have, and keep code to what is left.

2. 2

   Set the three things code time is for

   Fixing bugs. Building a feature that 3 or more people who fit your buyer asked for (step 7). Building the free tool in step 5. Nothing else.

3. 3

   Start a request sheet

   Make a Google Sheet with the columns: idea, who asked, how many people asked. Every feature idea goes in it, including your own. Your own ideas start at 0 people.

If handing marketing to someone else feels safer, wait. Founders who try to hire a marketer or find a marketing co-foundersoon before they know what works often report that it failed. Do it yourself for 4 weeks first, so you know what to hand over.

• Tool: Google Calendar and Google Sheets. Both free.
• Time: 30 minutes.
• You will have: a marketing block on every day, a code block after it, and a request sheet.
• It worked if: after 7 days, your calendar shows 35 hours of marketing, and git log --since="7 days ago" shows only bug fixes, requested features or the free tool.
• Common mistake: "one more feature before I launch". One developer wrote in August 2026 that he spent two years building tools nobody used, "answering engineering questions before answering the product question". He froze his features and started counting users instead.

2. Describe your product by the problem it fixes, not how it is built#

Write one sentence that says who your product is for and the moment their problem hurts, with no technology in it. Then make it your homepage headline.

Engineers describe what they built: the framework, the model, the API. Your buyer does not search for those. They search for the problem, in their own words. This one sentence is the heart of your ideal customer profile, and every other step uses it.

[Product] is for [kind of team or person] of [size] who [the moment the problem hurts], and today they [what they do instead].

Now turn the problem into the result: your value proposition. Put it in your homepage headlinesoon, with a "Try it free" button under it that leads straight into the product.

[What the user gets, in their words]. [How fast, or which pain goes away].[One line under it: who it is for.][Button:] Try it free

Cut these words from the headline and the sentence: the language or framework, "API", "AI-powered", "platform", "infrastructure", "open source" (unless your buyers are developers who choose tools by it). If you cannot name 20 real people with this problem, check the problem is real first.

• Tool: a Google Doc, your site editor, and ChatGPT or Claude to suggest 10 versions. You pick one.
• Time: 1 hour 30 minutes.
• You will have: the sentence, and a new headline live on your site.
• It worked if: you show the page to 10 people for 5 seconds, and at least 8 can say what it does and who it is for.
• Common mistake: writing it for other developers. If a stranger in your buyer's job has to scroll to understand it, they leave. If people understand the page and still do not sign up, fix the rest of the pagesoon next.

3. Message 100 people a day and ask for a 15-minute chat#

Send 100 personal messagessoon every day to people who fit your sentence. Ask for a short chat about their problem. Treat it as research, not selling.

This is the step technical founders skip, and the one that most often brings the first paying users. In an April 2026 Hacker News thread on marketing as a solo technical founder, one founder said the only thing that reliably worked was direct contact: find people who could use your product, and message them. Another, still solo at $100K a month, said to talk to every customer and ask why they signed up.

Think of it as debugging your market. You would not guess why a test fails; you would look. A chat shows you how people deal with the problem today, what it costs them, and whether they would pay.

Build the list. 100 messages a day needs about 3,000 names a month. List people who fitsoon by name: people you know first, then people who wrote about the problem online, then companies that fit your sentence. Find each person's emailsoon. Add 100 new names every day.

Let AI draft. Paste 10 names at a time into ChatGPT or Claudesoon, each with one thing you found about them, plus the template below. Ask for one message per person. Make the first line true and about them, then send. That is about a minute a message.

Send them one at a time. Use your normal email or LinkedIn. Gmail requires every sender to set up SPF or DKIM, two settings that prove your email really comes from your domain, and to keep spam reports under 0.3%. If you email more than about 50 strangers a day, set up a second domainsoon and warm it up first, so your main email stays safe. In the US, the CAN-SPAM Act covers business email too: every message needs your postal address and a way to say no, and you must honour a "no" within 10 business days. The UK and EU have stricter rules, so check them before you write to buyers there. LinkedIn limits how many invitations you send, and a block usually lasts a week, so message people you are already connected tosoon and send the rest by email.

Follow up and hold the chats. Follow upsoon twice with everyone who has not replied, 3 days apart, with one new line each time. Put a booking link in every reply: in Google Calendar, click Create, then Appointment schedule. On the call, ask three customer interview questions: How do you deal with this today? What did it cost you last time? What have you tried? Then, if it fits, show the productsoon and set up their trial while you are both on the call. Write each request they make in your request sheet, with their name.

Subject: [the problem, in 3–5 words]Hi [first name],[One true line about them: something they built, wrote or said.]I'm building [product] for [kind of team] who [problem]. I'm trying to learn how people like you deal with this today.Could I ask you 3 questions on a 15-minute call this week? If you want, I'll show you what I've built at the end.[Your name]
[Your company, postal address]
Not for you? Reply "no" and I won't write again.

• Tool: Gmail or LinkedIn, ChatGPT or Claude to draft, a Google Sheet to log each message, and a Google Calendar appointment schedule for booking. A CRMsoon can wait.
• Time: about 2 hours a day for the messages, 45 minutes for 100 new names, and about 45 minutes for the chats.
• You will have: 700 messages sent and logged in week 1, and 2,800 by the end of week 4.
• It worked if: you get at least 3 chats from every 100 messages. Below 2, rewrite the first linesoon so it is more about them, then send the next 100.
• Common mistake: turning the chat into a pitch, or explaining the architecture. Ask, listen, then show. The other mistake is stopping at 50 messages because nobody replied yet.

4. Answer 20 questions a day where your buyers ask for help#

Pick 5 online places where your buyers ask for helpsoon, and answer 20 questions a day across them, fully, without selling.

Technical founders are good at this. You answer hard questions every day. The catch is where. Go where your buyers ask, not where other founders talk. In June 2026, one founder wrote on Indie Hackers that a post there got 500 views and 50 comments in a day and "roughly zero" paying users. What worked was "answering the boring questions" in his buyers' own communities. The same goes for building in publicsoon: unless you sell to founders, that audience is not your market.

A place can be a subredditsoon, a Slack or Discord group, a forum, or a Facebook groupsoon. Read each place's rules page before you post. Reddit's own rules say to "participate authentically" and "do not spam". Spreading 20 answers over 5 places keeps you inside each one's rules. Search each place for your buyer's words for the problem, and sort by New.

Answer as if your product did not exist. Mention it only if it truly helps, and then say it is yours. AI can find questions and list the points to cover; write the answer yourself, from what you know.

[Answer their exact question in the first line.][2–3 steps that fix it, which work without any product.][Only if it truly helps:] Disclosure: I'm building a tool for this. Happy to share it if useful, but the steps above fix most of it.

• Tool: the search box on each site.
• Time: about 1 hour a day, 3 minutes an answer.
• You will have: 560 useful answers in 4 weeks, under your own name.
• It worked if: after 4 weeks, at least 5 signups say they came from one of these places.
• Common mistake: answering in developer or founder communities when your buyers are not developers or founders. The other mistake is a link in every answer. Moderators remove those, and accounts that keep doing it get banned.

5. Turn part of your product into a free tool and show it on Hacker News#

Take one job your product already does, and put it on a free page anyone can use without signing up. This is where your coding skill becomes marketing: a free toolsoon keeps bringing people who search for that job.

Founders on Hacker News describe this working in 2026. One runs an open-source file manager and says his most important channel is free online tools: people who search "online ftp client" or "online s3 browser" find his product. Another makes the landing page a limited, no-login version of the app itself, which kept more visitors than a normal page.

Pick the job. Choose one thing your product does that a stranger can use in under a minute, with no account and no setup. Check that people search for it: type the job into Google and see if it appears as a suggestion. That phrase is the page's title and URL.

Build it in your code hours. Keep it small enough to build in about a week of your 2-hour code blocks. Put one line at the end: "Need this for [the bigger job]? Try [product] free." Tag that link with a UTM parametersoon, so you can count signups from the tool.

Launch it once. If your buyers are developers, post it on Show HNsoon. The rules fit a free tool: they ask you to make it easy to try, ideally "without barriers such as signups or emails". Two things changed in 2026. Since March, Hacker News has been restricting Show HN posts for a while, mostly from people new to the site; its notice asks you to "get to know the community" first. And the section is crowded: a February 2026 analysis found 37.2% of Show HN posts stayed at 1 point. So if your account is new, comment helpfully on Hacker News every day for a few weeks first. If your buyers are not developers, launch on Product Hunt instead. Either way, reply to every comment within an hour, and the next day send each commenter the message from step 3.

• Tool: your own stack, and Hacker News or Product Hunt. Both are free.
• Time: about a week of code hours to build, then a launch day.
• You will have: a free tool live on your site, and one launch.
• It worked if: in its first 2 weeks, the tool brings at least 3 signups, counted by its UTM tag, and every commenter got a message.
• Common mistake: a tool that needs an account, or one that has nothing to do with your product. Also: asking friends to upvote. Hacker News says plainly that this is "not ok". If the launch brings nothing, find out why, but keep the tool: its search traffic grows after the day.

6. Publish one page a day that answers a question your buyer searches#

Set up Google Search Consolesoon once, then publish one page every day that answers a question your buyer types into Google or ChatGPT. You know the problem deeply. Write that down.

This is slow, so start it now. In G2's March 2026 survey of 1,076 software buyers, 51% said they now start their research in an AI chatbot more often than in Google, up from 29% a year before. You cannot appear in those answerssoon if they cannot read your site.

Do the setup once:

1. 1

   Add your site to Search Console

   Add a Domain property, verify it in your DNS, and submit your sitemap. It is free.

2. 2

   Check robots.txt

   Open yoursite.com/robots.txt. If OAI-SearchBot or "User-agent: *" is followed by "Disallow: /", remove those lines. OpenAI says sites that block OAI-SearchBot are not shown in ChatGPT search answers. It is one line on any technical SEO checklistsoon.

3. 3

   Skip special AI files

   Google says you do not need "new machine readable files, AI text files, or markup" to appear in its AI featuressoon. Spend the time on pages.

Then write one page a day. Good first pages:

• The problem, in your buyer's words, with the fix. Take the questions from your chats in step 3 and your answers in step 4. Check people searchsoon each one: type it into Google and see if it appears as a suggestion.
• "[Competitor] alternatives" for the tools your buyers compare you with. Keep your alternatives pagessoon fair: say where the other tool is better.
• What you learned building it, only if your buyers are developers. If they are, you can also copy the page to DEV. Add canonical_url: with your page's address to the post's front matter, so search engines know your site has the original (canonical URL).

AI makes one a day possiblesoon. Give ChatGPT or Claude the question, your notes and what people said in chats, and ask for a first draft. Then add what only you can: a real screenshot, a number from your product, a step you tested. Google treats many pages made to rank without helping anyone as spam, whether a person or AI wrote them. After you publish, open URL Inspection in Search Console and click "Request indexing", so the page gets indexedsoon sooner.

• Tool: Google Search Console, and ChatGPT or Claude to draft.
• Time: 30 minutes for the setup, then about 1 hour a page.
• You will have: 28 new pages in 4 weeks, each answering one real question.
• It worked if: URL Inspection shows "URL is on Google" within 1 to 2 weeks of each page. Once a month, ask ChatGPT your buyer's question and write down which tools it namessoon.
• Common mistake: writing "how I built it with [framework]" posts when your buyers are not developers. Other developers will like them; your buyers will never find them. The other mistake is judging search at week 4. Judge it at month 3soon.

7. Count your funnel every Sunday and build only what users asked for#

Every Sunday, fill in one row of numbers, see where each signup came from, and pick next week's features from the request sheet: only ones that 3 or more people who fit asked for.

You would not ship code without tests. Marketing is the same. Measure it once a week, the same way, and change one thing at a time.

Set it up once. Add one question to your signup form: "Where did you hear about us?" This is self-reported attribution. Tag every link you share with UTM parameterssoon. Then set up a funnel from signup to your main feature in PostHog. Its free plan covers 1 million events a month, with no credit card. The share of signups who use the main feature is your activation ratesoon.

Every Sunday, fill in one row:

Week | Messages sent | Chats | Answers posted | Pages published | Tool uses | Signups | Used the main feature | Paying
Where signups came from: messages | communities | free tool | launch | search | other

Then pick next week's code. Open the request sheet. Build a request only if 3 or more people who fit your sentence asked for it, in chats or from inside the product. Everything else waits. Asking your first userssoon what is missing is how the list fills up.

After 2,800 messages, decide. If a place brought 0 chats and 0 signups, stop it and give its hours to the place that brought the most. Search is the only exception: judge it at month 3. If many people sign up but few use the main feature, fix the first minutes of the product before you send more people. Leave paid adssoon until at least 10 people have paid you and you know which sentence brought them. When one place clearly works, choose the next channel to add.

• Tool: Google Sheets and PostHog, both free to start.
• Time: 30 minutes each Sunday.
• You will have: one row per week, and a short list of features you know people want.
• It worked if: you can name where every paying customer came from, and every feature you built has 3 names next to it.
• Common mistake: counting GitHub stars, upvotes and likes instead of chats and signups. The other mistake is building for one loud user.

Where Scout7 helps#

Scout7 speeds up three of the seven steps: 2, 4 and 6.

Step 2. Scout7's audience research reads public social conversations in your category and builds audience segments with pain points and quotes in buyers' own words. That gives you their words for your sentence and headline. It does not replace the chats in step 3.

Step 4. Join Conversations searches social platforms for live discussions about your problem, groups them by the kind of reply that fits, and drafts a reply in your voice. You read each thread yourself and approve or rewrite the reply. Nothing is posted without your approval.

Step 6. Keyword intelligence shows monthly searches, difficulty, and who leads on Google and in AI answers for each term. AI question coverage collects the questions buyers ask AI assistants in your category and shows who gets cited. Together they give you a list of pages to write, one for each day.

Your technical founder marketing checklist for the next 4 weeks

0 of 21 done

Work through this list with an AI assistant

It drafts the work and keeps track of what is done.

Do this with ChatGPT(opens in a new tab)Do this with Claude(opens in a new tab)

Step 1 · Stop adding features and put marketing first in your day

• Block the first 5 hours of every day for marketing, and put a 2-hour code block after it.
• Start a request sheet and move every feature idea into it.
• Every dayDo your marketing block before you open your code editor.

Step 2 · Describe your product by the problem it fixes

• Write one sentence: who your product is for, their size, and the moment the problem hurts.
• Rewrite your homepage headline as the result the user gets, and test it on 10 people for 5 seconds.

Step 3 · Message 100 people a day and ask for a 15-minute chat

• Every daySend 100 personal messages asking for a 15-minute chat, and log them.
• Every dayAdd 100 new names to your list.
• Every dayFollow up with everyone who has not replied, up to twice, 3 days apart.
• Every dayHold every chat you booked, ask the three questions, and offer to set up the trial on the call.
• Make a booking link with a Google Calendar appointment schedule.

Step 4 · Answer 20 questions a day where your buyers ask for help

• Pick 5 places where your buyers ask for help, and read each one's rules.
• Every dayAnswer 20 questions across your 5 places without selling.

Step 5 · Turn part of your product into a free tool

• Build a free, no-signup tool from one job your product already does.
• Launch the tool once on Show HN or Product Hunt, and message everyone who comments.

Step 6 · Publish one page a day that answers a question your buyer searches

• Set up Google Search Console, submit your sitemap, and check robots.txt.
• Every dayPublish one page that answers a real buyer question, then request indexing.
• Once a monthAsk ChatGPT your buyer's question and write down which tools it names.

Step 7 · Count your funnel every Sunday and build only what users asked for

• Add "Where did you hear about us?" to your signup form and set up a signup-to-main-feature funnel.
• Every SundayFill in one row of the Sunday sheet, with where each signup came from.
• Every SundayPick next week's features from the request sheet.
• After 2,800 messagesStop anything with 0 chats and 0 signups, and move its hours to what worked.

Copy listDownloadReset