Trust that has receipts.
Speedruns, thin notes, low interaction, and diagnostic spam move the score. Effort is not self-reported.
FXF
Build better products, together.
Find the friction with real testers. Guide users through what remains. Handle consent without adding another monthly bill. FXF gives founders the feedback and product tools to fix what matters.
Join early. Bring something real to test.
The FxF suite
Find the problem. Show the way. Cover the boring legal part.
01Feedback
02Tours
03Consent
Feedback
Stop collecting opinions. Collect evidence.
A real person gets stuck. They pin the exact element. FXF brings the route, console error, and failed request with them—then sends the whole thing where your team already works.
- Human tasks and in-product annotations
- Bounded diagnostics, never session replay
- GitHub, Linear, Jira, and ClickUp handoff
Tours
Show them. Don't write another help doc.
Build the tour on your live product by clicking what matters. Cross pages. Wait for the actual click, form submit, field change, or application event.
The runtime is open source. The visual builder, delivery, and analytics are the part that saves your afternoon.
Consent
Legal boilerplate shouldn't be a subscription.
Check the services you use. Get a privacy policy, cookie table, hosted page, and consent banner that blocks optional scripts until the visitor decides.
Build yours freeA generated starting point, not legal advice. Because pretending otherwise would be legal advice.
The machinery behind the promise
Useful tools fail when the incentives are garbage.
Your NDA. Their signature.
Upload the PDF. Re-gate on every new version. Keep who accepted what, when, and from where.
Find your people by problem.
Founder circles expose real tester demand and active products by niche—not another dead community feed.
Code when you want it.
Identify users, pass context, and open tours from the SDK. The tour runtime is zero-dependency and open source.
The founder perspective
Your time—or your money.
Every product pays for feedback. If you do not have the budget, pay with effort. Test another founder's work honestly and earn the same attention for yours.
Mutual help is not charity. It is a practical advantage for builders who refuse to confuse compliments with progress.
THE HARD TRUTH
Your project might suck. Find out now.
A bad test is cheaper than a bad launch. Fail early, learn fast, and keep what works. Founders do not need another pat on the shoulder. They need the truth while there is still time to act.
In testing right now
Real products. Real feedback.
These founders chose to show their work while it is being tested. Sign up, try one, and tell them what actually breaks.
Frequently asked. Honestly answered.
No comforting lies.
Building is risky. Avoiding reality only makes it more expensive.
Do I need a campaign to use tours or consent?
No. Feedback campaigns, product tours, and consent setups are separate tools. Use one. Use all three. We do not manufacture dependencies to make the suite look clever.
Are diagnostics just session replay with better branding?
No. FXF captures bounded console errors, failed request metadata, and context attached to a pinned note. No video, keystrokes, request bodies, cookies, or continuous surveillance.
Is FXF only for polished products?
No. Bring the rough prototype, the confusing onboarding, or the feature you are unsure anyone needs. Early is when feedback is cheapest to act on. If nothing can change, you waited too long.
What if people say my project sucks?
Then you learned something valuable before wasting six more months. Silence is not validation. We expect honesty with evidence: the problem, the context, and enough detail to act.
Do I need to be a developer?
Not for campaigns, the tour builder, or the consent generator. Installation is a script tag. The SDK and open-source tour runtime are there when code is the better answer.
What if I am not an expert tester?
You do not need a certificate to notice confusion. Say what you expected, show where you hesitated, and explain why you stopped. Honest attention beats invented expertise.
Pricing
Free.
Every product pays for feedback. Test other founders' work and earn credits, or buy credits and get back to building. Same result either way: real people, real tasks, real opinions about your product.
The fine print. There is none.
What does one credit actually buy?
One full test run — every task in your campaign, completed by a real person, on your product. Five tasks and you want ten full test runs? Budget 10 credits. You pay for finished work — not clicks, not impressions, not "engagement."
What if a tester quits halfway?
You do not pay. Credits leave your balance when a test run is completed, not when it starts. Whatever is left comes back when you close the campaign.
Do credits expire?
No. Bought or earned, they sit in your balance until you spend them.
Why not a subscription?
Because you do not need feedback every month — you need it when you ship something worth testing. Pay for that, not for the months in between.
Is the feedback actually worth a credit?
Testers earn only for finished test runs, and their feedback feeds their Trust Score. Low-effort answers cost them access to better campaigns. The incentives point the right way.
Where do my first 10 credits come from?
From us. Finish founder onboarding and we drop 10 credits in your balance — enough for ten full runs of a five-task campaign. Test more to earn more, or buy them outright.
Free accounts include one campaign with up to five tasks, one connected app with one five-step tour, and one consent setup with a hosted policy and banner. Need more? Tell us what you are building — we read every request.
Create an accountFind us on
