I built reach for 14 days. Then realized I had nowhere for it to land.

The morning after I shipped my Build-in-Public post #6 (Stripe webhook silently failing for 5 days), I got a question that hit:

"PR is great. But how do I actually turn this into deals?"

Honest answer: I didn't have one.

In 14 days I'd built:

• 26 blog posts on the company landing page
• A Zenn technical post (Japanese)
• A dev.to technical post (English)
• 50+ URLs indexed in Google Search Console
• Search clicks growing from 0 → 40

The PR was working. But "And then what?" had no answer.

The structural problem: no landing page for the leads

Picture the funnel for a reader of my Stripe webhook incident report:

1. They read the technical post on dev.to → reach
2. They click my profile to see who wrote it → bio
3. They think "interesting, who is this person and how do I hire them?" → no answer → bounce

My company landing page (tasteck.tech) is for buyers of the SaaS — store owners and individual operators in Japan's nightlife industry. Nothing there speaks to "I read your Stripe debugging post and want to hire you for a NestJS spot project."

PR reach × landing page quality = deals. If the second factor is zero, multiplying the first one harder doesn't help.

What I shipped in one day

A. Built /work in Next.js (~30 min)

A consulting page at tasteck.tech/work. Contents:

• 4 services, tiered by engagement size:
  • 1-hour tech / industry consult: ¥5,000 ($33)
  • Stripe / billing design review: from ¥30,000 ($200)
  • NestJS / Next.js spot dev: from ¥100,000 ($670)
  • Build-in-Public ghostwriting / ops: from ¥50,000 / month ($335)
• 10 concrete achievements, not vague claims:
  • 8 years of running a niche-SaaS in production
  • 1467× query speedup on a slow report endpoint
  • Stripe incident: full repair in 4 hours
  • Multi-feature release executed in a single day (April 15)
  • EC2 migration with no downtime
  • 14-day Build-in-Public campaign with measurable SEO lift
  • Two products in beta concurrently
  • Multilingual content rollout (JP + EN)
  • 14-column CSV export for tax filing
  • Full rebrand
• English CTA for international readers (hourly $40)
• FAQ: cross-industry OK / NDA / process / payment terms
• Contact: mailto:[e-mail] direct (no form yet)

☝️ The achievements section started at 4. A friend pointed out, "your past commits and blog posts are full of bigger wins than what you're claiming." That outside view doubled the credibility of the page. SaaS operators are too modest about themselves.

B. Wire up 6 channels in the same day (~15 min)

Just having the page isn't enough — readers don't go hunting. So I added a "I'm available, here's where" signal everywhere:

• Header nav on tasteck.tech → "Consulting" link
• Footer same
• sitemap.xml (priority 0.85)
• dev.to bio: website_url, summary, available_for, skills_languages, location — all rewritten in English
• Zenn (Japanese tech platform) website URL → tasteck.tech/work
• X bio: added "🛠 Consulting → tasteck.tech/work"
• X pinned tweet: replaced "company intro" with "consulting available"

Six surfaces, one day.

C. Request GSC indexing (~1 min)

URL inspection → "Request indexing." Done.

Design decisions

Transparent pricing

Hiding numbers means people who can't afford you waste your time. Putting ¥5K / ¥30K / ¥100K / ¥50K-month up front filters in only the people who actually have the budget. Funnel quality > funnel volume.

Tiered services as a stairway

1-hour at ¥5K is a low-friction entry. Monthly retainer at ¥50K is the ceiling. The intent: someone might come in for the cheap consult, find it useful, then escalate to spot dev → ongoing retainer. Turn one-time encounters into multi-stage relationships.

Cross-industry / English explicitly OK

I run a vertical SaaS in Japan's nightlife industry. But my technical stack (Stripe / NestJS / Next.js / TypeORM / AWS) is fully transferable. So the FAQ explicitly says "non-industry projects welcome, English inquiries welcome." That single sentence dramatically expands the addressable market.

mailto: over Stripe Payment Link / Google Forms

For the first inquiries, lower friction wins. I want to read what people are asking before deciding whether structured intake is even useful. Once volume justifies it, I'll add a form.

Audience layers

Three concentric circles:

Layer	Source	Likely ask
Domestic SaaS founders / side-project devs	Zenn, X, landing blog	Stripe webhook bug fixes, NestJS spot work, 1-hour consults
International SaaS devs	dev.to, GitHub	NestJS / Next.js spot dev, Build-in-Public ghostwriting
Nightlife industry shops	Landing page TOP	Custom development on top of my SaaS, ops outsourcing

Confidence ranking: Layer 1 highest (warm Japanese audience), Layer 2 next (right after each English post), Layer 3 slowest-burn.

What I'm measuring (Day 15-21)

• GA / GSC pageviews on /work
• mailto: link click count
• Actual inquiry email volume
• Conversion to paid engagements + ARPU
• Referrer breakdown

I'll publish raw numbers in Build-in-Public post #8 in two weeks.

Takeaway

The "right" order would have been: ship /work first, then drive PR at it. I did it backwards.

But there's a silver lining to the wrong order: the credibility section on /work is filled with specific, dated, verifiable achievements because the PR phase forced me to document them. A /work page launched on Day 1 with no track record would have been forgettable.

If you're a SaaS operator running PR and wondering where the deals are: spend half a day shipping a landing page for the leads. The ROI on subsequent PR changes the moment that page exists.

---

Original Japanese version: Build-in-Public 第 7 弾
Hire me: tasteck.tech/work — non-industry projects welcome, English OK
Previous post: Stripe webhook silently failing for 5 days