Back to database

Lucas Werthein, Cactus's AI use case

Founder / operator at Cactus

Uses AI to turn personal routine data and business context into a lightweight reflection loop, while also using synthetic customer profiles to stress-test ideas, messaging, and assumptions.

The problem

What was broken before AI

Personal routine data is often scattered across apps, devices, notes, calendars, and memory. A wearable might show sleep or activity, but it does not always connect that signal to meals, stress, routines, energy, or goals in a useful way. Business research has a similar problem: founders may have assumptions about customers, but not enough structured conversations to test every angle before making decisions.

What changed

What the use case made possible

Lucas uses AI as a reflection layer over messy context. For personal routines, the model can help summarize logs, notice patterns, and turn scattered observations into better questions or small experiments. For business work, synthetic customer profiles let him pressure-test ideas from multiple perspectives before spending time on a larger research or sales motion.

Why this matters

Why this use case is worth studying

This use case is useful because it treats AI as a pattern finder rather than an authority. A person can bring in data, notes, and goals, then use the model to make the next reflection clearer: what changed, what might be related, what is worth tracking, and what question should be taken to a real person or expert.

Use this when

When this pattern applies

Use this pattern when you have scattered notes, tracked signals, or customer assumptions and need help turning them into better questions. It works especially well when the next step should be a small experiment or a real customer interview.

Exponential Builder analysis

01

Reflection gets better when context is gathered first.

AI is most useful here after the messy inputs are brought together: tracked signals, notes, goals, recent changes, and business assumptions. The model’s value comes from helping the builder see relationships that are hard to notice when everything lives in separate places.

02

Ask for questions before answers.

Lucas’s approach keeps the model in a safer, more useful role: summarizing, comparing, and suggesting what to investigate next. That matters because personal routines and customer behavior both produce tempting patterns that still need human judgment and real-world validation.

03

Synthetic customers are rehearsal partners.

Using AI-generated customer profiles can sharpen messaging, objections, and interview plans before a founder talks to real people. The key is treating those profiles as preparation for research, with the actual decision-making grounded in real customers, experts, or lived context.

Who this is for

Best fit

Founders testing customer assumptions

Operators tracking personal routines

People using wearables or habit logs

Coaches and consultants preparing client questions

Product teams exploring customer personas

Anyone who wants AI to support reflection without making final decisions

What to avoid

Mistakes and warnings

Where this pattern can go wrong if you copy it too literally.

Do not treat AI as a final authority.

Avoid uploading sensitive personal data without understanding privacy settings.

Do not let synthetic customers replace real customer conversations.

Keep experiments small and low-risk.

Be careful with patterns that sound convincing but are based on too little data.

Public workflow preview

The shape of the workflow

A high-level look at how the use case works, with the reusable pattern made clear.

01

Gather the raw signals

Lucas starts with notes, tracked signals, or customer assumptions that are normally scattered across tools.

02

Put the context in one place

AI becomes more useful when it can see goals, constraints, and recent history together.

03

Ask for patterns, not decisions

The model looks for themes and questions worth exploring rather than final answers.

04

Turn observations into small experiments

A pattern becomes a habit test, customer question, or hypothesis to verify.

05

Bring people back into the loop

Important conclusions still get checked with real customers, experts, or people with lived context.

Copy the pattern

The reusable idea

Pattern in one sentence

Use AI to turn scattered signals into clearer patterns, questions, and small experiments that still get validated by humans.

Reusable idea

Lucas’s workflow is a good reminder that AI reflection works best when it helps you ask better questions. If your information is scattered, start by collecting enough context for the model to see patterns. Then ask it to name what might be worth investigating, what changed recently, and what small experiment would make the next step clearer.

Steal this workflow

Run a weekly reflection loop with one personal or business question:

1

Pick one focus area: energy, sleep, workouts, habits, customer objections, or product positioning.

2

Paste in the raw context: tracked signals, notes, calendar context, recent changes, assumptions, and your current goal.

3

Ask AI for patterns, changes, and possible relationships, with uncertainty clearly marked.

4

Ask for the 5 best questions worth investigating next.

5

Choose one low-risk experiment for the next week, such as tracking a variable, changing one routine, or asking one customer question.

6

At the end of the week, add the new results and ask what changed.

7

For business ideas, create 3 synthetic customer profiles only to prepare interview questions, objections, and messaging tests.

8

Validate anything important with real customers, professionals, or people with direct experience.

Suggested prompt

“I want to use AI as a reflection layer, not as a final authority. Here is the area I’m trying to understand: [energy / sleep / habits / customer behavior / product idea]. Here are my recent notes, tracked signals, assumptions, and relevant context: [paste context]. Please summarize the main patterns and changes you notice, separate stronger signals from weak guesses, and list the most useful questions I should investigate next. Then suggest three small, low-risk experiments or follow-up conversations I could run this week to learn more. If this involves customers, also create three realistic synthetic customer profiles and explain what each might find appealing, what might make them skeptical, and what I should ask in a real interview.”

Field notes

Get new AI use cases in your inbox

A short weekly note on how real people are using AI to save time, make money, build tools, and run their lives.

No spam. Just useful AI use cases.

Related use cases

Keep exploring nearby systems.

Browse all