Launch and grow a project

Goal

Take a project you are building and prepare its next launch or growth step: choose who it helps, improve the page they will visit, draft a focused campaign, and measure whether people reach a useful result. Keep the research, code, assets, and follow-up work connected to the same project.

This recipe works for a new application, a website, a tool, or an existing project you want more people to use. Start with the first project task if you still need a working example to show.

Use the launch planner to prepare a draft for your project. It runs in your browser without a Redgold account; continuing the brief with an agent needs account access. A prepared plan does not connect an advertising account or start paid delivery.

Prepare a plan in the browser

1. Open the launch planner. Enter the project name, its public HTTPS destination, the intended audience, and the useful outcome you can offer them.
2. Set the calendar month and total USD allowance. Review the Search allocation and reserve; the defaults are USD 200 total, USD 150 for Search, and USD 50 reserved. Enter actual prior spending and other unpaid commitments for that month. Zero is only correct when you have checked that nothing is owed.
3. Reconcile the numbers with your budget ledger and provider accounts before marking spend reconciled. The checkbox records your check; it does not read billing accounts. Resolve any validation or budget issues the planner shows.
4. Copy the generated agent brief into your project conversation, and download the JSON plan to keep the budget status and tracking links with your launch work. The download also includes the full brief and per-channel URLs.

The planner prepares the draft locally. It does not save it to your account or retain it across visits, so copy or download anything you want to keep. Its publishing state stays blocked: a valid budget and completed brief are preparation, not permission or a live advertising connection. Follow the account, measurement, and launch steps below before any external action.

What you need first

• To work through the plan with an agent, a Redgold account and configured workspace. Access is currently invite-only; request access if needed. Work in the website or download the terminal client.
• Your project description and any relevant repository, website, screenshots, or source material. Connect only the repositories the task needs.
• A real next step for visitors: try the product, download it, request access, book a conversation, or buy. Use the action that actually works today.
• A monthly marketing allowance, including advertising, fees, taxes, and any tools or model usage you charge to marketing.

An agent can prepare research, copy, assets, implementation changes, and a campaign handoff with the tools available to your account. Direct publishing, ad-account changes, and recurring monitoring depend on connected tools and separate authorization. This guide does not imply that Google Ads or Reddit Ads is connected to your Redgold account.

For paid delivery you also need your own advertising account, billing setup, and permission to manage the campaign. Analytics access and Search Console access do not grant advertising-account access. Keep passwords, API keys, and payment details out of prompts and campaign files.

1. Give the agent a project brief

Fill in this prompt in a project conversation:

Help me build, launch, and grow [project].
It helps [people] accomplish [specific result].
Current state: [idea, working prototype, public product, or existing business].
Project sources: [repository, website, and material you may use].
Available proof: [real example, demo, user result, or none yet].
Visitor's next step: [working URL and action].
Total marketing budget: USD 200 per calendar month, including fees and tools.
Already spent or committed this month: [amount and breakdown].

Choose one initial audience and explain why the project helps them.
Prepare the next useful deliverable, a landing-page review, campaign drafts,
tracking links, a conversion checklist, and a budget ledger.
Separate verified facts from assumptions. Use real evidence in claims.
Keep ads and public posts in draft. Tell me which connections are missing.

If you do not know the audience yet, supply the problem and existing evidence. Ask the agent to recommend a starting audience and explain the alternatives. Choosing an audience for one campaign does not limit what your project can become.

2. Make the destination useful

Before paying for traffic, the destination should explain who the project helps, show the result, and offer one working next step. Keep a download easy to find when installing the product is that next step.

Have the agent check the headline, a concrete example, access requirements, pricing or expected costs, and the actual form or download flow. For a website change, inspect the mobile layout and verify links after deployment. For an invite-only product, explain what happens after an access request; do not promise immediate signup.

Search visibility also needs readable page content, a relevant title and description, canonical URLs, a sitemap, and useful links between related pages. Search Console can show indexing and search performance for a verified property. A successful technical check does not establish search rankings or customer demand.

3. Set one shared monthly budget

This worked example gives the whole project USD 200 per calendar month:

Reddit starts with an organic post, where community rules allow it. There is no separate Reddit ad allowance in this example. The reserve is unspent until you allocate it, and the USD 150 Search allocation is a ceiling, not a spending target. If other marketing costs need more than USD 50, reduce the Search allocation. An existing subscription counted against marketing belongs in the same ledger; this example is not a Redgold plan price.

Track the calendar month, currency, spending source, actual charges, accrued but unbilled spend, remaining commitments, and unallocated balance. Do not add unbilled spend twice when it becomes a charge. Use one ledger across channels and record reporting delays rather than treating missing spend as zero.

A daily ad budget is a pacing setting, not a guaranteed daily or combined monthly cap. Check the provider's current charging rules and any enforceable account or campaign limits before launch. Keep room for reporting delays and fees. If a requested ceiling cannot be enforced or reliably supervised, leave the campaign paused and use the unpaid work in this recipe.

4. Prepare a campaign you can review

Ask for one complete draft with the following fields:

Keep the initial paid experiment on one channel. A USD 200 total budget usually does not support useful learning across several ad networks at once. Search is a starting hypothesis when people already search for the problem; if the agent cannot identify relevant searches, keep paid delivery paused and use direct conversations, useful content, and community feedback first.

An organic Reddit draft should explain a relevant problem, show something useful, disclose your connection to the project, and follow the specific community's rules. Review the destination and community before authorizing a post. Preparing a draft is not permission to publish it or contact people.

5. Connect a visit to a useful result

Use consistent campaign links, for example:

https://your-project.example/launch?utm_source=google&utm_medium=cpc&utm_campaign=project_launch_2026_10&utm_content=outcome_a

For an approved community post, use utm_source=reddit and utm_medium=organic_social with a distinct utm_content. These are naming examples; replace the domain, campaign, and destination for your project. Do not put email addresses, account identifiers, credentials, or other personal information in tracking parameters.

Choose one primary conversion that reflects the working offer. Record an access request after the server accepts it, a purchase after payment succeeds, or an activated user after they complete their first useful task. A button click is an intermediate event; a download does not prove installation or activation. Keep those stages separate in reports.

Verify a complete journey from a tagged link through the successful action. Check that failed submissions do not count, repeated callbacks do not double count, and internal testing can be excluded. Apply the relevant consent and privacy settings for your analytics and advertising tools. If cross-domain attribution is unavailable, document that gap instead of inferring paid conversions from all-source totals.

6. Authorize the exact launch

Review the destination, copy, account, targeting, tracking, dates, and budget together. Then authorize that specific campaign or post, including whether the agent may pause it. An approval for a draft or a website change does not authorize buying ads, posting to a community, or increasing spend.

Use a connected provider tool only when it exposes the needed controls. If the connection is unavailable, the deliverable is a reviewed handoff for the advertising dashboard. Record the campaign identifier and inspect its actual state after launch; a prepared file or accepted request is not proof that ads are delivering.

7. Observe and improve

While a paid campaign runs, review it at a cadence that fits its possible spend. For this small example, plan a short daily review of spend, search terms, destination health, and conversion tracking, plus a weekly decision about the offer. Use the provider dashboard or explicitly configured monitoring; creating a plan does not create a scheduled agent job.

Track visits, accepted requests or purchases, first useful tasks, and revenue separately. Report cost per conversion only when the denominator and attribution are known. With small numbers, show the counts and uncertainty; a handful of clicks does not establish a winning audience or ad.

Ask the agent for the next concrete improvement: fix a broken step, clarify copy, answer a repeated question, remove irrelevant searches, or address a product problem. Give any helper an explicit scope. Observing user problems does not itself authorize changing their projects or accessing unrelated data. Bound the monitoring's model usage inside the same marketing allowance.

Pause paid delivery when tracking or the destination breaks, when spend cannot be reconciled, or before the remaining allowance risks being exhausted. A scheduled report is not a real-time spending control. Increasing a budget, adding a channel, or resuming delivery requires the applicable authorization.

Expected result and recovery

You should finish with a useful project improvement, a reviewable campaign draft, tagged links, a checked conversion journey, and one shared budget ledger. A launched campaign additionally needs its provider identifier, confirmed state, and an assigned monitoring responsibility.

Continue

See the launch and growth overview, the public website repair case study, and managed deployment verification. The common task index links to the other tools you can use as your project develops.