Vibecode WithJuly
track this build5 steps, step by step0%NOT REALLY · don't bother
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 project pack4 files · fastest path to a working personal build
You are building a lean indie version of WithJuly. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # WithJuly indie build ## Goal Build the smallest trustworthy replacement for the core WithJuly workflow for one developer or a tiny team. ## Scope A local dashboard with a public media kit page, a deal pipeline board, rate notes, deliverable checklists and payment reminders. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Inbound brand demand: no deals arrive because you built a pipeline - Benchmark rate data from real closed deals across comparable creators - A human or process pushing negotiation and follow up on your behalf - Brand-side trust, contracting and payment collection when a sponsor goes quiet - Deal terms review, exclusivity and usage-rights sanity checks If those capabilities are essential, use WithJuly instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief 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. ## Required capabilities - Node 20 and a local Postgres or SQLite file - A domain or subdomain if you want the media kit page to be public - Your own audience numbers, pulled or pasted in manually - Optional: a Stripe or invoicing tool for the actual money ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of WithJuly. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # WithJuly indie build ## Goal Build the smallest trustworthy replacement for the core WithJuly workflow for one developer or a tiny team. ## Scope A local dashboard with a public media kit page, a deal pipeline board, rate notes, deliverable checklists and payment reminders. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Inbound brand demand: no deals arrive because you built a pipeline - Benchmark rate data from real closed deals across comparable creators - A human or process pushing negotiation and follow up on your behalf - Brand-side trust, contracting and payment collection when a sponsor goes quiet - Deal terms review, exclusivity and usage-rights sanity checks If those capabilities are essential, use WithJuly instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief 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. ## Required capabilities - Node 20 and a local Postgres or SQLite file - A domain or subdomain if you want the media kit page to be public - Your own audience numbers, pulled or pasted in manually - Optional: a Stripe or invoicing tool for the actual money ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of WithJuly. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # WithJuly product brief ## Problem 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. ## Product outcome A local dashboard with a public media kit page, a deal pipeline board, rate notes, deliverable checklists and payment reminders. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20 and a local Postgres or SQLite file - A domain or subdomain if you want the media kit page to be public - Your own audience numbers, pulled or pasted in manually - Optional: a Stripe or invoicing tool for the actual money ## Explicit non-goals for v1 - Inbound brand demand: no deals arrive because you built a pipeline - Benchmark rate data from real closed deals across comparable creators - A human or process pushing negotiation and follow up on your behalf - Brand-side trust, contracting and payment collection when a sponsor goes quiet - Deal terms review, exclusivity and usage-rights sanity checks ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted WithJuly capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# WithJuly indie build ## Goal Build the smallest trustworthy replacement for the core WithJuly workflow for one developer or a tiny team. ## Scope A local dashboard with a public media kit page, a deal pipeline board, rate notes, deliverable checklists and payment reminders. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - Inbound brand demand: no deals arrive because you built a pipeline - Benchmark rate data from real closed deals across comparable creators - A human or process pushing negotiation and follow up on your behalf - Brand-side trust, contracting and payment collection when a sponsor goes quiet - Deal terms review, exclusivity and usage-rights sanity checks If those capabilities are essential, use WithJuly instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief 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. ## Required capabilities - Node 20 and a local Postgres or SQLite file - A domain or subdomain if you want the media kit page to be public - Your own audience numbers, pulled or pasted in manually - Optional: a Stripe or invoicing tool for the actual money ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# WithJuly product brief ## Problem 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. ## Product outcome A local dashboard with a public media kit page, a deal pipeline board, rate notes, deliverable checklists and payment reminders. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Node 20 and a local Postgres or SQLite file - A domain or subdomain if you want the media kit page to be public - Your own audience numbers, pulled or pasted in manually - Optional: a Stripe or invoicing tool for the actual money ## Explicit non-goals for v1 - Inbound brand demand: no deals arrive because you built a pipeline - Benchmark rate data from real closed deals across comparable creators - A human or process pushing negotiation and follow up on your behalf - Brand-side trust, contracting and payment collection when a sponsor goes quiet - Deal terms review, exclusivity and usage-rights sanity checks ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted WithJuly capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
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.
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
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced WithJuly with one prompt"
Vibecode WithJuly
Not really. WithJuly's value is not the code: The moat is deal flow plus a private history of what brands actually paid, and neither ships with your repo. See the honest breakdown above.
How much does WithJuly cost?
WithJuly's pricing is usage-based or varies by plan · Page states 'Our minimum plan is $50/month' and '+$6/mo per creator, Billed Quarterly', but the per-manager base prices for Essentials/Pro/Growth are client-rendered and absent from the fetched HTML..
What do I lose by replacing WithJuly?
Honestly: Inbound brand demand: no deals arrive because you built a pipeline; Benchmark rate data from real closed deals across comparable creators; A human or process pushing negotiation and follow up on your behalf; Brand-side trust, contracting and payment collection when a sponsor goes quiet; Deal terms review, exclusivity and usage-rights sanity checks. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to WithJuly?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.