Can I vibecode WithJuly?

NOT REALLY · don't bother

price variesbuild time a weekendcategory 🛍️ creator commercereplaced by 0 people

The software layer here is thin: a media kit page, a deal pipeline, some invoices and reminders. The part that matters is on the other side of the table, meaning actual brand relationships, inbound demand, and rate data from deals that already closed. An agent can build you a very tidy place to track sponsorships you do not have yet. It cannot tell you what a 40k-subscriber tech channel really gets paid for a 60 second integration, and it cannot make a marketing manager email you. Build the tracker if you want, but do not confuse it with the thing being replaced.

the prompt

Build a local-first sponsorship deal tracker for a single creator. Consolation build: this replaces the paperwork, not the deal flow.

Stack, no substitutions:
- Next.js 15 App Router, TypeScript, Tailwind
- SQLite via Drizzle ORM, file at ./data/deals.db
- No auth, no accounts, no telemetry, no external SaaS calls
- Runs with: npm install, npm run db:push, npm run dev

Data model:
- brand: name, contactName, contactEmail, notes
- deal: brandId, status (inbound, negotiating, agreed, in-production, delivered, invoiced, paid, dead), platform, deliverables (text), grossFee (integer cents), currency, usageRights (text), exclusivity (text), agreedAt, dueAt, invoicedAt, paidAt, notes
- rateNote: platform, audienceSize, deliverableType, feeCents, dateClosed, source (mine or reported), notes
- asset: dealId, label, url

Pages:
1. /pipeline: kanban board by deal status, drag to move, inline edit of fee and due date. Show totals per column in currency.
2. /deals/[id]: full deal detail, deliverable checklist stored as JSON, timeline of status changes, asset links.
3. /rates: table of rateNote rows plus a simple median and range calculator filtered by platform and deliverable type. Make it obvious that this is your own data only and that an empty table means you know nothing yet.
4. /money: unpaid deals sorted by days overdue, computed from invoicedAt, with a copy-to-clipboard chase email drafted from a template.
5. /kit: a printable one-page media kit. Audience numbers are typed in by hand and stored in a single settings row. Include a static export script that writes ./out/kit.html for hosting anywhere.

Explicitly out of scope, do not build: brand discovery, any marketplace or matching, contract e-signing, payment processing, OAuth to YouTube, TikTok or Instagram, benchmark data you did not enter yourself.

Include seed data with three fake brands and six deals across statuses. Put any future API keys in .env.example, none are required to run. README: one paragraph on setup, one paragraph stating plainly that this tracks deals and does not source them.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

Creators do not pay for the pipeline UI, they pay for deal flow and for not being the one who has to email a brand asking where the money is. The rate data is the quiet second reason: knowing that similar creators charged more is worth several times the subscription on a single negotiation. Both of those are byproducts of volume that already flowed through the platform, and no amount of good code manufactures volume on day one.

what you lose

xInbound brand demand: no deals arrive because you built a pipeline

xBenchmark rate data from real closed deals across comparable creators

xA human or process pushing negotiation and follow up on your behalf

xBrand-side trust, contracting and payment collection when a sponsor goes quiet

xDeal terms review, exclusivity and usage-rights sanity checks

prior art · use these instead of building, if you'd rather

Nothing worth pointing at. That's why the prompt exists.

share on X ↗"I just replaced WithJuly with one prompt"