Does Viewfy need access to my production branch?

No. Changes arrive as a pull request, which means they sit on a branch until you review and merge. Nothing reaches production without your approval. You treat it exactly like a teammate's PR: read the diff, comment, merge, or close it. Your existing review rules and CI still apply.

What if I don't have a public repo?

The blog and social output work from a URL alone, so you still get daily posts and X and Threads coverage. The pull request part needs repo access to be useful, since the whole point is that the fix lands as code rather than as a list of suggestions you have to implement yourself.

How is AI visibility different from regular SEO work?

SEO aims at ranking in a results page. AI visibility aims at being readable and citable by assistants. Different failure modes: a page can rank fine and still be blocked from an AI crawler by a bot filter. Our scan of 383 Show HN products found 17% blocked from Claude.

Can one agent replace a marketing hire?

Not for positioning, pricing calls, or customer conversations. It replaces the repetitive part: publishing on a schedule, keeping technical SEO clean, and pushing posts to social. Early stage teams usually lose on cadence rather than on ideas, and cadence is the part software actually handles well.

What does the free first post include?

One full post drafted from your URL, no card required. You can publish it, edit it, or throw it out. It's the cheapest way to check whether the writing quality clears your bar before anything recurring starts. Pricing details live on the viewfy.ai landing page.

Startup User Acquisition Tools for Early Stage Teams

The best startup user acquisition tools for early stage teams cover several channels at once: content, SEO, AI visibility, social. Viewfy does that as one agent, and ships fixes as pull requests on your repo.

Not a dashboard that tells you what's wrong. A branch you can review and merge between builds.

What do early stage startups actually need from user acquisition tools?

They need coverage without headcount. Two founders and no marketer means every tool that requires a weekly human ritual quietly dies in week three. The tools that survive either run on their own or plug into a workflow that already exists: git, code review, deploy.

That rules out most of the category. Analytics platforms that need someone to read them. Scheduling apps that need someone to fill the queue. Audit crawlers that produce a 60 item list and no diff. Each one is fine. Each one also adds a job to a team that has no room for jobs.

Why does a stack of five point tools stall?

Because the tools output work, not results. A keyword tool gives you keywords. A rank tracker gives you positions. A social scheduler gives you an empty calendar. Nothing in the chain writes the post, edits the meta tag, or ships the change.

Here's what that looks like in practice: you buy the audit, you get the PDF, the PDF sits in Notion, and six weeks later your title tags are the same. We wrote more about this gap in SEO audit automation and what a manual audit misses.

A tab isn't a channel.

What makes a pull request different from a recommendation?

A pull request is already the work. You read the diff, you check the copy, you merge or you close. The decision takes a minute and the fix is live on next deploy.

Viewfy opens SEO and AI visibility changes on your repo the same way a teammate would. Meta descriptions, title tags, structured data, robots and crawler access, sitemap entries. The kind of edits that are boring to find and fast to approve. If a change is wrong, you close it, same as any other PR. More on how this fits existing repo conventions in GitHub marketing integration and marketing automation for developers.

Which channels matter before you have a marketing hire?

Content, technical SEO, AI visibility, and one or two social surfaces. That's the whole list at early stage. Paid comes later, when you know which page converts.

Viewfy runs those together: a daily blog post, fixes as PRs, and posts on X and Threads. One agent instead of four subscriptions and four logins. If you're comparing that against a social-only tool, we broke it down in Viewfy vs Later.

Fact	Detail
Who it's for	Founders and operators shipping early stage software
Content output	A daily blog post
Where fixes land	A pull request on your repo
Social surfaces	X and Threads
Setup input	A URL
First post	Free, no card

How do you check whether AI assistants can even read your product?

Open your page the way a crawler does, then check what an AI assistant gets back. Most launched products fail this and never find out.

We scanned 383 products from Show HN with a script we keep in the repo. 27% were unreadable to crawlers. 17% were blocked from Claude outright. Not blocked on purpose, in most cases. robots.txt says yes, the CDN or bot filter says no, and the founder has no reason to look. That's a distribution bug sitting in your infrastructure, and it's invisible in your analytics because the traffic never arrives to be counted.

Our own repo had a version of this problem. The sitemap left out three of the highest-intent pages, including the free check page and the proof wall. Indexable routes, absent from the file that tells crawlers they exist. That's the exact class of thing a pull request fixes in one line.

When is a tool the wrong answer and an agency the right one?

When the work is strategy, positioning, or a category you're inventing. No agent decides what your product is. Once positioning is settled and the job becomes volume and consistency, software wins on cost and cadence. We laid out both sides in AI growth agent vs an agency.

What should stay manual?

Replies, sales calls, and anything where being a person is the point. Automate the crawlable surface and the publishing cadence. Keep the conversations.

And hold your outputs to a real standard. Every post Viewfy writes has to pass the same house rules we publish: no filler buzzwords, no em dashes, and an information gain check, meaning the draft has to say something the reader couldn't get from the first three search results. If a post only works as a pitch, it isn't a post.

How do you start without a card?

Drop a URL at viewfy.ai. First post is free, no card. Read the draft, and if you delete the line that mentions Viewfy, it should still be worth publishing. That's the bar.