your ai product manager.

bevel watches your posthog, github, and users, tells you what to ship next, hands you the work to do it, then checks if it actually worked.

or let's talk
is the dashboard worth finishing?
bevel
reading your last 3 weeks of commits
pulling feature usage · posthog
scanning your user chats for what they ask for

honestly, no. you're building the wrong thing.

3 weeks of commits went to the dashboard. 0 of 40 users have opened it. meanwhile 12 asked for csv export.

ship that instead. here's the spec:

claude code prompt csv export · 9 lines 
# bevel · ticket · paste into claude code

add csv export to the data table.

put an "export csv" button on the table toolbar.
export the current filtered view, not everything,
and match the column order shown on screen.

stop building the analytics dashboard.
run pnpm typecheck && pnpm lint after changes.
track impact
bevel

tracking. i'll tell you if shipping export moves retention.

usage
how it works

bevel does the product manager's job. watch, decide, hand off, verify.

it finds what you'd miss. bugs, leads, gaps, momentum.

bevel reads your analytics, your repo, your users, and the open web, then surfaces what actually needs you: the leak in your funnel, the founder asking for your product on reddit, the competitor who just dropped pricing. ranked, with evidence, and tuned to your stage.

autopilot scanning
ticketsscanning for more

raise free cap 250 to 1k issues

teams bounce after 7d at cap. lever.

startdismiss

dm the 8 power users who hit cmd+k

they tried to summon nothing. ask why.

startdismiss

audit linear pricing drop

$29 to $9. you need a story.

startdismiss

bevel writes new ones as it scans your product + reads your chats.

quick actions
  • interview a recent signup
  • draft this week's update

hands you the work, done. artifacts, not advice.

whatever the move needs: 20 named leads with a drafted dm, the launch post, the spec, the competitor teardown, or a prompt for your coding agent. you review it and send it. the gap between deciding and doing is one click.

bevel

raising the free-tier cap from 250 to 1,000 issues. evidence is consistent and the prior raise in wk 9 paid off; this one should too. paste the prompt into claude code.

claude code prompt 4 lines 
# bevel · ticket · paste into claude code
raise free-tier issue cap 250 to 1,000
update src/app/pricing/page.tsx to match
fire the in-app warning at 80% of new cap
add a regression test: cap_hit fires at 1,000

know if it actually worked. the receipt.

ship a ticket and bevel snapshots the metric it should move. days later it comes back with the verdict: moved, flat, or wrong call. you stop guessing whether the work mattered.

every receipt compounds in bevel's memory
bevel
pulling posthog · activation funnel
comparing to the baseline from may 7

the cap raise worked.

you shipped it thursday. activation went 24% to 31% in 14 days, and the deploy is the only change that touched the funnel.

called it

→next bet: the pricing page

one bet at a time. pick a direction. everything re-tunes.

commit the week to distribution, launch, or polish. every ticket and every chat answer pulls toward it. switch any time and the tickets re-tune within the hour. no 40-item backlog.

the path day 3 of 10
distribution-first active

land your first 50 founders this week. stop everything else.

signals
9 dau spike after show hn
icp active on indie hackers
skips
shipping, polish
founder-led sales is the job
if you pick this
dm 10 founders from the hn thread
fix the auth leak blocking signups
post the changelog while traffic holds
expansion bevel's lean active

go public. show hn, product hunt, twitter. spike awareness.

signals
landing converts warm traffic
launch assets already drafted
skips
conversion polish
cold visitors will bounce
if you pick this
show hn post, written and timed
product hunt assets + first comment
a launch-week tweet thread
product perfection active

polish until the next visitor becomes a fan.

signals
session replays show confusion
low traffic = cheap to fix now
skips
distribution
nobody sees it until you switch
if you pick this
fix the 3 confusing first-run steps
cut onboarding to one screen
close the top 5 ux papercuts

switch any time. tickets re-tune within the hour.

the new stack

claude code is vibe coding. bevel is vibe producting.

cursor is the how. bevel is the what. run both and the loop closes.

vibe coding

you say “build me X”. the agent writes the code.

claude code, cursor, codex. you type the change, the agent runs the keystrokes. solves how. assumes you already know what to ship.

vibe producting

bevel is what tells you the X.

it watches your product and the open web, writes the next ticket, and hands your coding agent something worth building. then it checks whether the ship moved a number.

bevelthe WHAT claude codethe HOW posthog aidashboard ai linear / asanabacklog
writes tickets across code, posts, outreach, research ●···
watches posthog + github + vercel + the open web 24/7 ●·partial·
hands you the executable next move ●···
comes back with the number after you ship ●···
memory across decisions; learns your taste ●···
why it sticks

recommendations are cheap. the loop is not.

01 · real names

20 prospects. not vibes.

ask “find me 20 founders to interview” and bevel pulls real named people from hn, reddit, and linkedin, each with the post you can open. nothing fabricated.

j*** · "i'd pay for this"hn
m*** · 87 upvotesr/saas
p*** · launch · 12dhn
02 · the loop

comes back to ask if it worked.

click ship and bevel remembers your numbers. queues a check-in: 3 days for outreach, 14 for pricing copy, 30 for retention. the next ticket asks whether it moved.

check-in · 14 days

“did the cap raise move activation?”

03 · every move

every move counts. code is one verb of five.

track impact fires on outreach, landing copy, pricing experiments. anything you actually go do counts.

code outreach post research watch

the how side of building is solved. cursor, claude code, and lovable turn any idea into shipped code. the what side is still a guess. bevel closes it: watch the product, decide the move, hand over the work, come back with the number. the full loop of product discovery.

pricing

free during beta. flat after. no credits, no meters.

solo beta · free
$0while in beta

the cockpit. posthog + github + vercel, soft caps, full autopilot.

  • autopilot · always on
  • connect posthog, github, and vercel
  • soft caps to stop runaway use, not to squeeze you
  • memory across every chat
start the autopilot
founder coming soon
$20/mo · flat

all sources. unlimited tickets. switch the path any time.

  • connect every source · always on
  • unlimited tickets + chats
  • impact tracking on every ship
  • bevel’s failed runs are free. always.
available after beta
team coming soon
$99/mo · flat

2-5 founders sharing one product memory.

  • shared cockpit · shared memory
  • custom sources · MCP
  • direct line to the maker
available after beta

find out what to ship tonight. 3 tickets from your first scan.

paste your url. the first scan runs while you watch. the next one runs while you sleep.

or let's talk