Feedback just got smarter.

The middle man finally has a tool.

Point at what's wrong. Get the right fix, fast. No more sloppy feedback. No more bottlenecks.

Web pages, internal tools, PDFs, Claude artifacts. If it opens in your browser, you can mark it up.

DDana Tue 4:12 PM
Looked at the dashboard. A few things:
  • the 2nd chart is wrong, not the frist one the one under it
  • numbers on teh right dont match what we talked about
  • can the button on the left be like more obvious
  • also the thing at the bottom the grey part make that bigger??
  • and somethign looked off on the SOP pdf page 3ish i think
14 minutes of toggling tabs. Three follow-up questions. Two things fixed wrong.
with Fixnote
DDana Tue 4:03 PM
Notes on the dashboard and the SOP, all in one place:
Dashboard-changes-v2.docx5 tickets · 5 screenshots · dashboard + SOP page 3
FN-01Revenue chart: use the 12-month series
FN-04SOP p.3 line 12: 1/8" → 3/16"
ops.yourcompany.com/dashboard

Weekly operations dashboard

Revenue is shown for the trailing 6 months across all locations. Figures update nightly.

Export CSV
Press Space
Comment on this text
“trailing 6 months”
main > p:nth-of-type(1)
CancelSave
Fixnote1Send report
Your report is ready
3 tickets across 2 pages · Dashboard
PRO
FN-01Change “trailing 6 months” to the 12-month series
FN-02Right-align the prices in the two summary tiles
FN-03SOP page 3, line 12: change 1/8" to 3/16"
Word documentIncludes screenshotsMarkdown + screenshotsFor Claude, Cursor, Codex
CaptureTypeSend

Yes, we used it on ourselves. This page was reviewed with Fixnote. The feedback that built it arrived as one document, not forty Slack messages.

The problem

You know the cycle. It just flipped.

It has never been easier or quicker to build: artifacts, dashboards, analyses, SOPs, whole apps. What didn't get faster is the human on the other side, looking at what got built and getting clear feedback back. Building used to be the bottleneck. Now feedback is.

Each bar is one round: build, get feedback, build again. Same story, three eras.

Before

Building was the slow part

BuildnotesBuildReview
weeks per roundfeedback was the small part

Weeks of development, then a quick review at the end. Notes could be sloppy — there was time to sort them out.

Now

Feedback is the slow part

ClaudeChatGPTCursor
BuildWaiting on feedbackBuildWaiting again — “not that one, the other one”Build
days per roundAI shrank the build. The wait didn’t move.

The work is done in an hour, then it sits: vague notes, screenshots, three follow-up questions, two things fixed wrong.

With Fixnote

Nothing is waiting

BuildFixnoteBuildFixnoteBuild
same afternoonno blockers

Ten minutes, once: point, type, send. One clean report a person or an AI acts on immediately — and the build never stops.

starttime →
50%

of pull requests sit idle for more than half their lifespan, waiting on a human.LinearB benchmarks, 8.1M pull requests

57%

of developers say unclear requirements are what slows their work down.ManekTech developer survey, 2025

10+ hrs

a week lost to friction outside of building, for half of all developers.Atlassian State of Developer Experience, 2025

Capture. Type. Send.

Fixnote lives in your browser toolbar. It does nothing until you click it, then it works on any page, PDF or artifact you can see.

1Capture

Point at it

Highlight text and press Space. Or click an element, or drag a box around any region. It stays lit while you type.

claude.ai · artifact
Order pipeline
Approve batch
2Type

Say what should change

A sentence is enough. The note carries the location, the current text and a screenshot, so you don't have to describe where.

Refacing-SOP.pdf · page 3
3.1 Measure the opening at three points.
3.2 Subtract 1/8 inch for the overlay gap.
3.3 Confirm hinge side with the customer.
Comment on this text
“1/8 inch”
Change to 3/16 inch. Update the diagram on page 4 to match.
3Send

One report, all in one place

Every note across every page and file lands in one clean document. Word for people, Markdown for AI.

Your report is ready
Ops dashboard · Requested changes
FN-01Use the 12-month revenue series
FN-02Right-align prices in summary tiles
FN-03SOP p.3: 1/8" → 3/16"
FN-04“Approve batch” needs a confirm step
Download .docx

What comes out

A clean, organized, dynamic changelog.

Not a pile of screenshots. A document with every requested change, where it is, what it says now, and what it should say, ready for a teammate, a vendor, or a coding agent.

  • 1
    All in one placeWeb pages, PDFs and artifacts in the same report. Forward one file, once.
  • { }
    The exact spotElement or page-and-line, with the current text, so nobody fixes the wrong thing.
  • v2
    Rounds you can followv1, v2, v3 per project. Continuous improvement instead of a fresh argument each time.
  • AI
    Built for AIPaste the Markdown into a coding agent with “implement every ticket” and it does.
Claude CodeCodexCursorCopilotWindsurfLovableBoltv0
Ops dashboard · Requested changes
Prepared by Dana · September 12, 2026 · 4 tickets · 2 files
IDChangeWhere
FN-01Use the 12-month revenue series/dashboard
FN-02Right-align prices in the summary tiles/dashboard
FN-03Change 1/8" to 3/16"SOP p.3 l.12
FN-04Add a confirm step to “Approve batch”artifact
FN-03 · Change 1/8" to 3/16"
DocumentRefacing-SOP.pdfLocationPage 3, line 12
Current text
“3.2 Subtract 1/8 inch for the overlay gap.”
Requested change
Change to 3/16 inch. Update the diagram on page 4 to match.
Screenshot

Who it's for

Wherever the feedback gets stuck.

If you're the one between the person who wants it and the person (or AI) who builds it, this is for you.

Mark up your Claude artifacts with ease.

Claude built it in a minute. Fixnote works inside the artifact: hover the element, type the change, export Markdown, paste it back. It writes the next prompt for you.

ClaudeArtifactsVibe coders
claude.ai · Work order tracker
Work order tracker
Mark shipped
Comment on this elementPut the ship date on this button once it’s marked shipped.
Claude artifact

Feedback on SOPs, proposals and specs.

Open the PDF in Fixnote, point at the line, say what's wrong. Every note references the page and line. The person who owns the document gets one list, not twelve emails.

PDFsSOPsProposals
Employee-Onboarding-SOP.pdf
4.1 Confirm the equipment checklist before the first shift.
4.2 Inspect every item for damage or missing parts.
4.3 Photograph anything damaged before signing.
4.4 Report issues within 48 hours.
p.4 l.2add “and missing labels”
p.4 l.448 hours → 72 hours
p.5diagram is the old version

Review the build once. Get it back right.

Your developer is in another time zone and bills by the hour. Send a Fixnote report at night instead of a 40-message thread; the fixes are waiting in the morning, and “FN-04” means the same thing to both of you.

FoundersContractorsUpwork · Toptal
app.yourcompany.com/checkout
Review your order
Complete order
FN-01Hero headline cut off on mobile
FN-02Wrong phone number in footer
FN-03“Complete order” → “Place order”

Every location sends you complaints. Send one list.

Turn franchise complaints into feedback someone can actually act on. Your locations see the problems first — Fixnote turns what they send you into one report your vendor works through top to bottom.

Franchise HQMulti-location opsVendors
yourbrand.com/locations/atlanta
Atlanta showroom
Book now
FN-01Atlanta: hours wrong
FN-02Raleigh: map pin off
FN-03All: “Book now” hidden on mobile

Ship the landing page, then fix it in one pass.

You built it in an afternoon. Now every “move that up, wrong price, headline wraps” comes back as one numbered list your next prompt can work straight through — instead of five Slack messages and a screenshot.

Landing pagesSaaS foundersIndie hackers
yoursaas.com
One place for every change request
Start free
FN-01Headline wraps on mobile
FN-02Pricing toggle defaults to annual
FN-03“Start free” sits below the fold
“This is exactly what I was looking for. This is so much cleaner than what we used to use.”
Developer, on the receiving end of Fixnote reports
50+locations

Built and tested inside a 50-plus location network, with the dev team in mind. Used every week on internal tools, SOPs and Claude artifacts before it was ever sold.

Try it on the next thing you have to give feedback on.

Free account, no card. Unlimited notes and three Word reports a month. Pro when you rely on it.

Rely on it? See Pro and team plans. Works in Chrome, Edge, Brave and Arc.

Questions

What is Fixnote, exactly?

Fixnote is a Chrome extension for giving feedback on anything you can open in a browser: web pages, internal tools and admin panels, PDFs such as SOPs, proposals and specs, and Claude artifacts. You click an element, highlight text and press Space, or drag a box around a region, type what should change, and Fixnote captures the screenshot, the exact location and the current text. When you're done it sends one clean, organized change report: a Word document on every plan, or Markdown with a screenshots folder on Pro.

Does it work with Claude Code, Codex, Cursor and other coding agents?

Yes, and that's where the Markdown export shines. Each ticket carries the exact element (or page and line), its current text, the requested change and a screenshot, which is what Claude Code, OpenAI Codex, Cursor, GitHub Copilot, Windsurf, Lovable, Bolt or v0 need to make the change without a follow-up question. Paste the report with “implement every ticket” and review the diff. Fixnote also works inside Claude artifacts, so you can mark up what Claude just built and send the notes straight back.

Does it work on PDFs?

Yes, on Pro. Click the Fixnote icon on any PDF tab and it opens in Fixnote's viewer, where you can hover a line to pin a note to it or capture a region. The report references the page and line. You can also drop a PDF from your computer into the viewer. Google Docs and Word Online render as images in the browser, so on those Fixnote captures regions rather than lines.

Does the person receiving the report need Fixnote?

No. They get a normal .docx or Markdown file. It opens in Word, Google Docs and Pages, and pastes cleanly into Jira, Trello, Linear, Notion, GitHub issues or email. The ticket IDs (FN-01, FN-02…) give you both a shared vocabulary for the whole round.

Does it work on internal tools and pages behind a login?

Yes. Fixnote runs inside your browser on whatever page is open: admin panels, staging sites, CRMs, ERPs, internal dashboards and pages behind a login. There's no “add this snippet to your site” step and nothing to ask your developer for before you start.

Where does my data go?

Notes and screenshots stay in your browser until you export a report. When you export, the report is saved privately to your Fixnote account so you can find it later by project, and that's the only thing Fixnote ever receives. Removing the extension deletes everything it stored locally. Read the privacy policy.

How much does it cost?

Free accounts get unlimited notes and three Word reports a month. Pro is $13.99 a month or $119 a year: unlimited reports, Markdown with screenshots for coding agents, PDF markup, clean documents, and every report saved by project. Team plans with shared projects and one invoice are available by email. Cancel any time; Pro stays on until the end of the period you paid for.

Which browsers are supported?

Chrome, Edge, Brave and Arc (anything built on Chromium), on Mac, Windows and Linux. Safari and Firefox aren't supported yet.