The Wealth
Experiment
Join the free beta

Financial freedom starts with more choices

Build a side hustle.
Build your AI team.

Create room for useful work, earning options, and a life with more flexibility. Start with one repeatable job, give your agents a clear brief, and keep improving the system.

Make my personal team plan →Explore your productivity potential

Define freedom for yourself

What would more flexibility make possible?

A side hustle can be a way to test earning options. Better productivity can make room for learning, family, rest, or work you care about. Choose a concrete first goal: reclaim two hours a week, test one paid offer, or finish the project you keep postponing.

Financial freedom is an ambition to work toward. Track the actual time, costs, demand, and income as you go. Start with a test small enough to fit your life.

Turn that goal into one small experiment →

You set the direction

Give every agent a job.
Give the work a quality bar.

Think of a team as a set of roles with clear handoffs. You can practice with separate conversations in one assistant, then use connected agents when your chosen tool supports them. More agents help only when the work can be separated and checked.

01

Research scout

Bring back a short evidence brief with sources, dates, and open questions.

Your decision: Check the sources and decide which question deserves a test.

02

Project planner

Turn your chosen outcome into small tasks, dependencies, and a time limit.

Your decision: Choose the scope and what you will leave for later.

03

Maker

Produce a draft, design, prototype, or document from the approved brief.

Your decision: Decide whether it solves the actual problem.

04

Quality reviewer

Check the output against the brief; return specific defects and missing evidence.

Your decision: Verify the important checks yourself and approve the result.

05

Operations helper

Prepare repeatable checklists, organize approved files, and flag exceptions.

Your decision: Set access limits and approve changes to live systems.

06

Learning partner

Summarize actual feedback, costs, time, and what changed this week.

Your decision: Choose to continue, adjust, or pause the experiment.

Start with a maker and a reviewer. Add research or operations when there is a recurring job for them. One shared brief and an agreed output format make the next handoff easier.

Use the starting prompt
Act as my [role] for [project]. The outcome is [one finished output] for [audience]. Use only [approved inputs and sources]. Work within [time and cost limit]. Return [format], your sources, assumptions, and unresolved questions. Check against [acceptance criteria]. Hand the result to [next role] only when these checks pass. Stop for my decision before sending, publishing, spending, deleting, or changing a live system. Do not invent missing facts.

Go deeper: ten AI assistant roles and a first-week experiment →

A dozen places to start

Automate the repeat.
Keep the judgment.

Choose work that happens often, has usable inputs, and has a result you can check. These are setup ideas for your own tools; try a draft-only run before connecting live actions.

After a meeting

Meeting notes → next actions

Turn approved notes into decisions, owners, and a draft follow-up.

Keep this check: Confirm names, dates, and commitments before sharing.

Make a plan for this task →

At the start of your work session

Inbox → a useful triage list

Group messages into reply, task, reference, and needs-your-judgment.

Keep this check: Keep sending, deleting, and commitments under your control.

Make a plan for this task →

At your weekly review

Weekly work → a progress note

Collect completed tasks, blockers, time, and the next decision.

Keep this check: Reconcile the summary with your actual log.

Make a plan for this task →

After approving the main piece

One article → a content package

Draft a short post, email excerpt, and demonstration outline.

Keep this check: Preserve source context and review each piece before publishing.

Make a plan for this task →

When a question repeats

Customer questions → an FAQ draft

Group real questions and propose answers from approved material.

Keep this check: Check accuracy, tone, and which answers need a person.

Make a plan for this task →

Before a workshop

A rough outline → a teaching worksheet

Create an exercise, instructions, example, and answer guide.

Keep this check: Try the exercise yourself and remove ambiguous steps.

Make a plan for this task →

After several conversations

Feedback → a theme map

Group anonymized observations with links back to the evidence.

Keep this check: Keep disagreement and unknowns visible; do not invent demand.

Make a plan for this task →

Before a decision

A research question → a source brief

Organize approved primary sources, dates, and competing explanations.

Keep this check: Open important sources and verify the claims.

Make a plan for this task →

When an intake is complete

Client intake → a project brief

Prepare scope, missing questions, milestones, and a draft checklist.

Keep this check: Confirm scope and price with the client yourself.

Make a plan for this task →

After a successful delivery

Repeated service → a delivery checklist

Turn your process into a reusable template and exception list.

Keep this check: Test it on the next real job before relying on it.

Make a plan for this task →

Before implementing a change

A feature brief → test cases

List normal, empty, error, and mobile states with expected behavior.

Keep this check: Run meaningful checks and decide whether it is ready.

Make a plan for this task →

When you solve a repeated problem

A finished task → reusable instructions

Capture the inputs, steps, output, and common failure points.

Keep this check: Remove secrets and check that another person can follow it.

Make a plan for this task →

Which recurring job is worth setting up? Run the numbers →

See the handoffs

Four workflows you can borrow.

Each starts with your context and ends with a decision or a useful artifact. Use the prompts in the assistant you choose.

A small service, ready to test

For a side hustle based on something you already know.

  1. You choose a buyer and one problem.
  2. Research scout organizes real conversations and open questions.
  3. Planner scopes one small paid-pilot hypothesis; maker drafts a sample.
  4. Reviewer checks the sample against your promise and flags gaps.
  5. You show it to a relevant person, discuss scope, and record the response.
Open the detailed walkthrough →
Use the starting prompt
Use my skill [skill] and these real observations [notes] to draft one small service test for [buyer]. Return the deliverable, what is excluded, a sample outline, acceptance checks, and one question for a potential buyer. Label assumptions. Keep the test within [hours] and [budget].

One useful idea, several formats

For sharing expertise without starting from scratch every time.

  1. You approve a main article or demonstration with its sources.
  2. Writer drafts a post, email excerpt, and short video outline.
  3. Reviewer checks each version against the approved original.
  4. You adapt the voice, choose the channel, and approve publication.
  5. Learning partner organizes actual reactions into the next reader question.
Open the detailed walkthrough →
Use the starting prompt
Adapt this approved material [content and sources] into [formats] for [audience]. Keep the same factual claims and caveats. Give each piece one useful idea and a next step. Include a review checklist; do not publish or schedule anything.

A tiny tool, ready for someone to try

For turning a repeated problem into a useful first version.

  1. You describe one user, one task, and what “done” means.
  2. Planner writes a small brief and lists missing decisions.
  3. Maker builds the smallest usable version.
  4. Reviewer tries normal, empty, invalid, and narrow-screen cases.
  5. You approve release, observe a willing user, and choose the next fix.
Open the detailed walkthrough →
Use the starting prompt
Help me build [small tool] for [user and task]. Start with an approved brief, inputs, outputs, and acceptance checks. Keep version one within [limits]. Include empty, invalid, and mobile states. Return the artifact and evidence from meaningful checks. Pause before deployment for my review.

A week of work, one clear next move

For improving the system instead of only doing more.

  1. You gather the real time log, costs, outputs, and feedback.
  2. Operations helper organizes the records; missing data stays unknown.
  3. Learning partner compares the evidence with your original test.
  4. Reviewer offers another explanation for the result.
  5. You choose one change, a time limit, and the next review date.
Open the detailed walkthrough →
Use the starting prompt
Review this week [actual records] against my goal [goal]. Separate effort, accepted output, customer response, costs, and income received. State what is still unknown. Offer continue, change, and pause options. Suggest one small next test within [time and spending limits].

Your practice, with Waymaker

Build a routine.
Find your way through the dips.

Wealth Experiment is where you try the work and measure what you learn. Waymaker brings Builder DNA, founder stories, and Cameron, its AI Chief of Staff, into the wider journey. Start here with the shared assessment and stories, then use these original practice prompts with Cameron in your Waymaker workspace.

Before you build · 5 minutes

Make the next step fit today.

Name your energy, available time, and one output. Use Builder DNA as a reflection prompt: what strength can help, and what habit might get in the way? Try a 25-minute build block and leave a note for the next session.

Use the starting prompt
Help me choose one useful output for today. I have [minutes], my energy is [description], and my current experiment is [brief]. My Builder DNA reflection is [strength and growth edge]. Suggest a small first action and a stopping point. Ask for missing context rather than assuming it.

When momentum dips · 10 minutes

Make returning easier.

Open the last thing you made. Notice what stopped you: an unclear step, an oversized task, missing feedback, or simply too much on your plate. Choose a five-minute restart, a smaller test, or an intentional pause. Read one founder story for perspective, then return to your own next move.

Use the starting prompt
I stalled on [project] after [what happened]. The last thing I learned was [evidence]. Help me distinguish an unclear next step, a scope problem, a need for feedback, and a need to pause. Give me one five-minute restart and one sensible pause option. Do not turn a setback into a promised success.

At the weekly review · 15 minutes

Improve one part of the routine.

Compare your intended work with what happened. Keep the cue that helped you start, shrink a task that ran long, and remove one friction point. Record the next action before you close the project so the next session begins with less effort.

Use the starting prompt
Review my routine using [planned work, actual work, time, and friction]. What helped me start? Where did I lose time? Suggest one change to test next week, a way to measure whether it helps, and the first action for my next session. Keep the plan within [available time].

These routines are suggested exercises with adjustable time boxes. The quiz and story library work here; personalized conversations with Cameron take place in Waymaker.

Start this week

One job. Two roles.
A little more room.

Pick a recurring task. Time the manual version. Give a maker and reviewer one clear brief. Try the workflow, count the whole effort, and decide whether to keep it. Build your team around work that earns its place.

Free download · The Experiment Scorecard

Know if your side idea is actually working.

A 6-page scorecard for testing one income idea: the signal ladder, a four-week evidence log, the true-cost check, and a clear continue / change / pause decision. Download it now, with no signup required. You can also request occasional notes from Ashley’s experiments.

Download the free scorecard

Signups are stored with MailerLite. See the privacy page.