Gadarum.
For founders building what’s next

Stop guessing.Build whatcustomers want.

Gadarum gives founders one workspace to find the right customers, test demand, and turn customer feedback into clearer decisions and focused action.

Join Waitlist See Gadarum in action How it works

Your evidence. Your decisions. One connected workspace.

From customer signal to next moveExample
Customer feedback
“Useful report. But I need to share it with clients.”
A response worth understanding.
Venture Health
Useful value reportedSupporting
Sharing is a blockerNeeds attention
Your decision → your next focus

Test sharing before adding more.

A founder-chosen follow-up. Not an automatic decision.
Learn. Decide. Act. Repeat.
Conceptual workflow · fictional feedback, not a product screenshot.
Customer evidence, connected
One clear next focus
You stay in control
Less busywork. Better questions.

What’s keeping you
from your next move?

Start with the question that matters to your venture—not another list of features.

“Who actually
wants this?”

Test a defined customer profile or explore a mixed Group. See who responds, what you learn, and what still needs testing.

Find your market

“What should
I build next?”

Connect Features to customer problems, reported benefits, and blockers. Give your next product decision a stronger basis.

Build around customer needs

“Are we making
real progress?”

Review supporting signals, conflicting evidence, and open questions together. Understand where the venture stands—and why.

See the evidence picture

Already have a product or customer list? Start with the context you have. Keep learning from there.

Find your starting point
Powered by the Gadarum Engine

Don’t just collect feedback.
Give it somewhere to go.

Customer work creates evidence. Gadarum helps you review what it means, choose your next move, and put that decision back into action.

Venture Health makes the evidence understandable.

Supporting signals, conflicts, and gaps—not a magic success score.

Venture Memory keeps the recorded context.

Revisit important sources, decisions, and the reasons behind them.

Today's Mission gives the next step a place to happen.

Scheduled work and review needs come into one primary focus.

Explore the Gadarum Engine
One connected learning loop
01 / TEST

Start with
a question.

Choose a customer, problem, or assumption to test.

02 / CAPTURE

Record the
response.

Keep what happened connected to its source.

03 / REVIEW

Understand
the meaning.

See the support, contradictions, and open questions.

04 / DECIDE

Choose your
next move.

Make the call. Plan the work. Capture the next outcome.

The next customer interaction starts the loop again.

Your venture’s records connect the loop. Your judgment directs it.

More than a place to store information. A way to turn it into a better next question. Founder-led. Evidence-informed.
See the difference in practice

One customer response.
A more focused next move.

A simple example of how Product, Venture Health, and Today's Mission connect—without making the decision for you.

Interactive illustration. All feedback and decisions below are fictional.

A weekly reporting productIllustrative walkthrough
01 / Start with what happened

Keep the value.
Keep the “but.”

A prospect tries your weekly report. They describe a benefit—and a missing capability. Record both against the Feature, rather than turning a mixed response into a win.

Product gives the feedback context: which customer, which Feature, and what they actually reported.
02 / Review the meaning

The report helps.
The job isn’t finished.

Venture Health helps you review the observation alongside the broader evidence. A reported benefit can matter without making the blocker—or the unknowns—disappear.

A useful signal is a reason to investigate. It is not a declaration of product-market fit.
Supporting observation

The prospect reports saving time.

One customer observation; broader demand is unproven.
Needs attention

Sharing is part of the customer’s job.

The reported blocker may limit the Feature’s usefulness.
Still unknown

Does this matter to other customers?

Willingness to pay and repeat use are not established.
03 / Choose, then act

A narrower test.
Not a bigger backlog.

You choose to investigate sharing before adding more Features. Record that decision and schedule the customer work. Today's Mission gives it a place alongside your existing commitments.

You choose and schedule the work. New outcomes then give the next review something better to work with.
Illustrative founder decision
“Test report sharing with three prospects before expanding the feature list.”
Founder-scheduled follow-up

Follow up on the sharing blocker.

Learn how clients receive reports today—and what makes sharing useful.
The source stays connected. A customer observation is not automatically a validated conclusion.

Step 1 of 3 · Customer evidence

Validate. Launch. Grow.

Your venture evolves.
Your learning stays with you.

Different stages. Different questions. Keep the customer context and recorded decisions as your direction develops.

01 / VALIDATE

Find the signal.

“Is this the right problem and customer?”

Test Segments or Groups, capture customer responses, and review the evidence before committing to a direction.

Market tests, customer evidence, and review
Explore Validate
02 / LAUNCH

Put it to work.

“How do we turn interest into customers?”

Keep your Product, pricing history, Campaigns, and customer follow-ups connected. Broader Launch guidance is still being developed.

A connected commercial foundation
Explore Launch
03 / GROW

Keep learning.

“What is worth repeating?”

Carry customer and Product context forward. Dedicated retention and repeatability analysis is planned—not presented as available.

Growth intelligence is planned
Explore the Grow direction

A phase change doesn’t erase what you learned. You choose when to move forward—or revisit an earlier question.

Explore the full journey

Your venture. Your call.

Gadarum combines AI-assisted analysis with rule-based guidance. It helps you see the evidence—not automatically pick your market, set your price, or declare you ready to launch.

Meet the Engine
A few straight answers

Clear purpose.
No magic promises.

A practical system for learning from customers and choosing your next move.

What is Gadarum?

Gadarum is a connected workspace for founders to organize market tests, customer records, Product Feedback, evidence reviews, and decisions. Its purpose is to connect what you learn from customers with what you do next.

Who is it for?

Founders testing a business idea or developing an existing product. You can start with a customer hypothesis or bring the Contacts you already have. You do not have to be a technical founder to work through these questions.

Is this another AI chatbot or task manager?

The main value is the connection between customer evidence and execution. AI can help analyze; rules support interpretation and prioritization. Venture Health explains the evidence, while Today's Mission focuses the work. You remain responsible for strategic decisions.

Can I bring my existing customer information?

The documented workflows support Contact CSV import and a separate historical Notes import into existing Contacts. This is not a promise of complete CRM migration, automatic email history, or importing every type of customer record.

Will Gadarum tell me I’ve found product-market fit?

No. It helps you examine customer signals, conflicting evidence, sample limitations, and open questions. A positive response or a suggested Segment is not proof of demand. You decide what the evidence justifies.

Does Gadarum run campaigns or build the product for me?

No. It helps you define, organize, and review the work. You carry out customer outreach and build your product using the appropriate tools. Gadarum connects the recorded outcomes back to learning and decisions.

Your next move deserves
more than a guess.

Start with a customer question. See how the answer can lead to a more focused decision.

Join Waitlist Request early access to Gadarum.
Gadarum.

The Gadarum journey

Validate.Launch.Grow.

One venture. A continuous learning loop.

Find the right customers. Learn what turns interest into commitment. Build toward repeatable growth—with your evidence and decisions connected.

Explore the journey Find your starting point

You choose the phase. Your learning stays with you.

One venture, three questionsA connected path links Validate: Who needs this?, Launch: Will they commit?, and Grow: What can repeat? Customer learning carries forward. This is a conceptual illustration, not a product screen. THE QUESTION CHANGES. THE LEARNING STAYS. 01 / VALIDATE Who needs this? Test the audience. Understand the problem. 02 / LAUNCH Will they commit? Test the offer. Learn from the response. 03 / GROW What can repeat? Dedicated growth intelligence is planned. YOUR CUSTOMER LEARNING CARRIES FORWARD
Concept illustration, not a product screen. See current scope.
Customer evidence
Founder decisions
Connected execution

Your questions change.
Your learning shouldn’t disappear.

First: who needs this? Then: will they commit? Later: what can repeat? Each question builds on the work before it—not on another blank plan.

Gadarum connects customer work, evidence, and recorded decisions so your next move can build on what you have learned.

Different goals. Shared foundations.

Three phases.
One connected venture.

The goal changes. Your customers, evidence, and decisions stay in the same workspace.

Test a customer hypothesisA target highlights a customer among a wider group, with two notes ready to collect observations. A CUSTOMER PROFILE IS A HYPOTHESIS.
01 / Validate

“Am I solving a problem people care about?”

Replace broad assumptions with a focused customer test. Learn who feels the problem and what their responses actually support.

Focus on
The audience, the problem, and the evidence for demand.
How Gadarum helps
Test defined Segments or explore mixed Groups. Connect customer activity, Campaign results, and Product Feedback.
The decision it supports
Keep testing, refine your direction, or consider the next phase.
Explore the Validate path Core validation workflows
Learn from a customer responseAn offer and a customer response are connected. Presenting an offer is different from receiving a commitment. Your offer Their reply INTEREST IS NOT YET A COMMITMENT.
02 / Launch

“How do I turn interest into customers?”

Make your offer real. Learn how the audience responds to your message, pricing, and follow-through—not just the idea.

Focus on
The offer, customer conversations, and commercial response.
How Gadarum helps
Reuse Campaigns, customer records, follow-ups, and pricing history to organize the work and its evidence.
The decision it supports
Which audience, message, offer, or follow-up should you test next?
Explore the Launch path Foundation in place; guidance expanding
Ask what can repeatThree repeated customer records surround a question mark. Dashed connections indicate an open question, not a measured growth trend. ? REPEATABILITY NEEDS EVIDENCE OVER TIME.
03 / Grow

“What works well enough to repeat?”

Move from isolated wins toward understanding what lasts. Growth needs evidence over time—not just a promising first result.

Focus on
Repeatable acquisition, customer value, and sustained relationships.
The foundation to build on
Keep using the shared venture records and workflows. Dedicated growth interpretation is a planned extension.
The decision to work toward
What deserves more investment—and what still needs to be proven?
Explore the Grow direction Dedicated growth intelligence planned

The phases describe different business questions, not three equally complete feature sets. Review the product scope.

Powered by the Gadarum Engine

A new phase.
Not a new blank page.

Your recorded learning stays connected to the venture. The Engine brings together customer context, evidence review, founder judgment, and the next work.

Learning that carries forwardThree notes for customer context, evidence and decisions rest on the same Venture Memory foundation. CUSTOMERS EVIDENCE DECISIONS ONE VENTURE MEMORY
01 / CONTEXT

Know who you’re learning from.

Keep customer records, audience definitions, and product context connected.

02 / EVIDENCE

Understand what happened.

Review recorded outcomes, conflicting signals, and questions still unanswered.

03 / DECISION

Choose with the evidence in view.

Preserve the decision and its recorded basis. Your conclusion remains yours.

04 / ACTION

Bring the learning into the work.

Today's Mission brings scheduled tasks, reviews, and decision follow-ups into focus.

ActCaptureReviewDecideAct again

Venture Memory preserves context. It does not turn assumptions into facts.

Start with the question you face

Where is your venture today?

Choose the situation closest to yours. Explore the work, the decision, and the product support behind it.

All three paths are shown below. Enable JavaScript to explore them one at a time.

Validate / explore demandILLUSTRATIVE GUIDE

Learn who wants it.
And why.

Start with a specific question about the customer, the problem, or the reason to change. Gather responses before treating the idea as proven.

An example founder question

“I have a workflow tool and a mixed list of prospects. Who should I focus on?”

Choose what to test.

Test a defined Segment, or explore a mixed Group when the strongest customer profile is still unclear.

Do the customer work.

Plan conversations or Campaign activity. Record what happened, including objections, weak signals, and unanswered questions.

Review, then choose the next test.

Compare the observed patterns and their sample sizes. Decide whether to refine the audience, continue testing, or review the evidence for Launch.

Product scope: Segment and Group Validation, Campaigns, Product Feedback, evidence review, and founder decisions.

See the Validate foundation
Launch / test the commercial pathILLUSTRATIVE GUIDE

Move beyond interest.
Learn what earns a customer.

Build on what you know about the audience. Make the offer concrete, follow through, and keep the actual commercial response separate from your hopes.

An example founder question

“People ask about pricing. I need to understand what helps them take the next step.”

Make the offer explicit.

Bring together your audience, Campaign message, proposed offer, and the exact pricing terms you are presenting.

Follow through and record the response.

Use scheduled customer work and follow-ups. Keep interest, objections, and recorded payment distinct; an observation is not independent transaction verification.

Decide what to improve.

Review the available customer and pricing evidence. Choose the next audience, message, offer, or follow-up to test. Unified Launch guidance is still being expanded.

Product scope: Shared Campaigns, customer records, follow-ups, and versioned pricing. Broader phase-aware guidance is not complete.

See the Launch foundation
Grow / ask what can repeatILLUSTRATIVE GUIDE

Don’t just chase more.
Understand what can last.

The growth question is not simply whether customers buy once. It is whether value, customer relationships, and acquisition can hold up over time.

An example founder question

“We have some customers. What evidence would justify investing more in growth?”

Keep the current customer context.

Continue using the shared Contacts, Campaigns, Product Feedback, pricing, and recorded decisions in the same venture.

Identify the evidence you still need.

Ask what would demonstrate repeat purchasing, retention, and repeatable acquisition. A positive “use again” response is not a retention history.

Build toward growth interpretation. Planned

Dedicated retention, churn, and repeatability analysis are planned. The present foundation does not certify that a venture is ready to scale.

Product scope: Shared venture workflows and an explicit Grow phase. Dedicated growth intelligence remains planned.

Understand the Grow scope

Illustrative guidance, not a readiness assessment. Selecting a path here does not set a phase, create work, or change your venture.

You choose the directionA founder decision card sits above Validate, Launch and Grow. Arrows allow both forward movement and revisiting earlier questions. FOUNDER DECISIONYou choose the next move. ValidateLaunchGrow REVISIT. DON’T ERASE.

You set the direction

Progress isn’t always
a straight line.

You may arrive with an existing business. You may uncover a new assumption after launch. Neither means you should erase the work you have already done.

Start from your actual situation—not a compulsory checklist.
Keep testing new questions, even after you launch.
Choose phase changes explicitly. Retain the recorded learning.
Understand phase decisions

The vision, with the scope made clear

Connected by design.
Honest about the depth today.

The shared foundation spans the journey. Deeper phase-specific guidance is being developed in stages.

PHASE
EXISTING PRODUCT FOUNDATION
IMPORTANT BOUNDARY
ValidateThe deepest current workflow
Existing foundation

Segments and Groups, Campaigns, customer outcomes, Product Feedback, evidence review, Venture Health, and Today's Mission.

Important boundary

Evidence informs the founder. It does not certify product-market fit or guarantee that the market is ready.

LaunchCommercial foundations
Existing foundation

Shared Campaigns, customer context, normal follow-ups, Product information, and versioned pricing with linked evidence.

Important boundary

Unified Launch interpretation and general phase-aware Today's Mission guidance are not complete. Selected commercial actions remain release-controlled.

GrowShared workspace; planned insight
Existing foundation

An explicit Grow phase and the same customer, Campaign, Product, pricing, and decision records. Earlier learning is retained.

Important boundary

Dedicated retention, churn, repeat-purchase, and repeatability analysis are planned—not presented as available here.

About this preview: these descriptions reflect the supplied product-development reviews, not a verification of the live release. Illustrations are conceptual. This page does not run outreach, process payments, or change any venture data.

A few straight answers

A journey.
Not a rigid checklist.

No automatic graduation. No magic readiness score. Keep the evidence visible and the decision yours.

Do I have to start in Validate?

No. You can bring an existing venture and explicitly choose its phase in Settings. Prior learning can inform your starting context; entering Launch does not mean Gadarum conducted or certified your earlier validation.

Can I keep validating after I launch?

Yes. You can test a new audience, message, offer, or product assumption while the venture is in Launch. Validation is ongoing work, not a stage you are forbidden to revisit. Changing the venture phase is a separate founder decision.

Does a finished product mean the venture is ready to launch?

No. Product stage, feature delivery, and venture phase describe different things. A working product does not by itself establish demand, pricing acceptance, or a repeatable way to acquire customers.

Does Gadarum decide when I move to another phase?

No. You explicitly choose the phase. Evidence review can inform your judgment, but no universal score or automatic transition makes the strategic decision for you. Selecting a phase is not proof that its business goals have been achieved.

Is Grow a full growth-analytics product today?

Not yet. The shared venture workspace and Grow phase are part of the foundation. Dedicated retention, churn, repeat-purchase, and repeatability analysis are planned extensions, not capabilities this page presents as available.

What happens to my learning if I change direction?

Existing customer records, evidence, and recorded decisions remain in the venture when you change its phase. Earlier findings keep their original context; changing a phase does not turn an old assumption into newly validated evidence.

Your next chapter.
Built on what you learn.

Start with the question that matters now.
Carry the learning into what comes next.

Find your starting point Review the product scope
Gadarum.

Market Validation · Powered by the Gadarum Engine

Find your market.With evidence.Not guesswork.

Test who needs what you’re building. Capture what people say and do. Use the evidence to decide where to focus next.

See validation in action Find your starting point

You choose the market. Gadarum helps you test the case.

Two ways to test. One evidence-led process.A defined Segment or an exploratory Group leads to real customer activity, recorded signals and unanswered questions, then a founder-chosen direction. Conceptual illustration, not a live product screen. MARKET VALIDATION / THE BIG PICTURE TEST A HYPOTHESIS Defined Segment “I think this is my customer.” EXPLORE THE PATTERN Exploratory Group “Let’s see who responds.” REAL PEOPLE. RECORDED OUTCOMES. What did you actually learn? Positive signals Barriers, objections, and open questions EVIDENCE INFORMS. YOU DECIDE. A direction worth testing.
Conceptual illustration. Not a live dashboard or product screenshot.
Start with a question
Test with real people
You make the call

“Interesting idea”
is not a validated market.

You’ve had conversations. Collected feedback. Heard encouraging things. But who really has the problem—and what are they prepared to do about it?

Gadarum helps you move from scattered reactions to a focused test: a clear audience, real customer work, and evidence you can examine.

Start from what you know

Know your audience? Test it.
Not sure yet? Explore it.

Two different starting points. Neither requires you to pretend you already know who your best customer is.

A focused customer hypothesisA target highlights a defined customer profile from a larger set of people. This is a hypothesis to test, not an automatically validated audience. A DEFINED CUSTOMER PROFILE

01 / Segment Validation

“I know who I want to test.”

Define a specific customer profile. Then test whether those people have the problem and respond to your approach.

  • Set the customer criteria you want to test.
  • Choose Contacts and plan relevant activity.
  • Review the evidence for that specific audience.
Explore Segment Validation
Explore a mixed audienceDifferent customer profiles sit together in a founder-curated Group. Their recorded responses can be compared without pretending they are a single proven Segment. DIFFERENT PROFILES. OBSERVABLE PATTERNS.

02 / Group Validation

“I need to see who responds.”

Start with a mixed Group of Contacts you choose. Explore how different customer profiles respond before narrowing your target.

  • Bring together people you want to learn from.
  • Compare recorded outcomes by customer profile.
  • Review suggested Segments when supported.
Explore Group Validation

You can add or import Contacts. A Group does not need one shared customer profile, and creating a Segment does not declare it validated.

From a question to a better next move

A test should lead somewhere.
Not end in another spreadsheet.

One connected workflow—from choosing whom to test to deciding what the results mean for your next move.

Make customer work a repeatable practiceAn illustrated activity plan connects a scheduled conversation, its recorded outcome, and a founder-planned follow-up. It is not an automated sending system. PLAN03Contacts / day CAPTURE FOLLOW UP SMALL, REPEATABLE STEPS.
01

Choose your audience.

Start with a defined Segment or a founder-curated Group.

02

Prepare your Contacts.

Select the people you intend to learn from. Add or import existing Contacts.

03

Plan a meaningful test.

Set the question, message, offer, and next step. Give the work a schedule.

04

Record what happens.

Capture outcomes, observations, objections, and relevant supporting evidence.

05

Review the evidence.

Look at patterns, sample sizes, conflicting signals, and what remains unknown.

06

Choose your next move.

Continue, refine, or change direction. You decide what the next test should be.

Gadarum plans and tracks customer work. You carry out outreach through your chosen channels; it is not automated sending.

One product idea. Two ways to learn.

What would you learn
from this test?

Explore a fictional weekly-handoff tool. Switch between the two methods, then follow the question, activity, evidence, and decision.

Choose an example

Group Validation example

Group Validation / exampleFictional data

Which customer profile feels the problem?

You’re exploring a tool for weekly team handoffs. You have access to a mixed Group, but haven’t settled on one target customer.

Your hypothesis
Weekly handoffs are painful enough for some teams to consider a different way of working.
Your exploratory Group
18 Contacts: 10 operations managers and 8 company owners.
What you want to learn
Who reports the problem—and shows a reason to keep talking?
Founder-curated audienceNo single profile required

This Group is a place to explore. It is not a representative sample of the market.

Give each conversation a purpose.

You plan Direct Outreach to the Group and work through the Contacts. Gadarum keeps the work connected to the audience you are testing.

ActivityCustomer calls
Daily plan3 Contacts
PurposeLearn, then follow up
  • Ask about the last time the problem happened.
  • Understand the workaround they use today.
  • Explore a useful next step and record the response.

Example customer question

“Walk me through the last handoff that went wrong.”
An illustrative prompt—not an automatically generated sales script.

You make the calls and record the outcomes. Scheduling a call is not evidence that it happened.

A stronger response. Still a small sample.

After the test, compare the latest recorded outcome for each Contact by their current role. Keep neutral outcomes separate.

Operations managers6 of 9 positive

10 Contacts · 6 positive · 3 negative · 1 neutral

Company owners2 of 6 positive

8 Contacts · 2 positive · 4 negative · 2 neutral

Positive-signal counts use positive + negative outcomes as the denominator. The 3 neutral outcomes are not included in those denominators.

A reason to investigate, not proof of a market.Positive responses do not establish willingness to pay, statistical significance, or product-market fit.
What is behind this comparison?Open the fictional example’s basis and limitations

18 fictional Contacts; one latest outcome per person. Operations managers: 6 positive, 3 negative, 1 neutral. Company owners: 2 positive, 4 negative, 2 neutral.

Roles reflect current Contact information, not reconstructed historical attributes. This compares one profile dimension. It does not prove a combination of industry, role, and company size works best.

Campaign totals are not added to Contact outcomes. All data here are invented for this demonstration.

Turn a pattern into a question worth testing.

An evidence-supported candidate can give you a starting point. You review its definition and decide whether to create a Segment.

Illustrative founder decision
“Test operations managers more closely before narrowing our market.”

Basis: a stronger observed response in this exploratory Group, with a small sample and unresolved questions.

Next question: Is the problem urgent enough to try a different workflow—and what would prevent a trial?

Creating the Segment does not validate it. Earlier Group evidence remains Group evidence; it is not automatically reassigned.

Segment Validation example

Segment Validation / exampleFictional data

Does this specific customer profile respond?

You have a clear hypothesis for the same weekly-handoff tool. Now you want to test it with a defined audience.

Your customer profile
Operations managers at service businesses with 11–50 employees.
Your test audience
12 Contacts selected for this Segment.
What you want to learn
Are handoff problems urgent enough to explore a different workflow?
RoleBusiness typeCompany size

These criteria are your starting hypothesis. Setting them does not establish demand.

Test the same question with the chosen audience.

Plan Direct Outreach for your Segment. Keep the message, learning objective, and recorded outcomes connected to this test.

ActivityCustomer calls
Daily plan3 Contacts
PurposeLearn, then follow up
  • Ask about the last time the problem happened.
  • Understand the workaround they use today.
  • Explore a useful next step and record the response.

Example next-step question

“Would it be useful to walk through a different approach?”
Capture the actual answer—including hesitation or rejection.

You perform the outreach. A planned activity, a response, and a completed follow-up are different things.

Some interest. Important questions remain.

Of the 12 selected Contacts, 10 have a recorded outcome. Two do not yet have one. Missing outcomes are not negative evidence.

5Positive
4Negative
1Neutral
2No outcome yet
Recorded positive signal5 of 9 positive

Denominator: 5 positive + 4 negative. Neutral and missing outcomes are excluded.

This does not answer whether people will buy.Use the negative responses and open questions to shape the next conversations—not just the positive count.
What does this result include?Open the fictional example’s basis and limitations

12 fictional selected Contacts. One latest recorded outcome per Contact where available: 5 positive, 4 negative, 1 neutral, and 2 without an outcome.

The positive count summarizes recorded responses, not purchases. A positive response in this example means interest in a practical follow-up. It does not imply a trial, signed agreement, or payment.

This is a small, selected audience—not a market-wide estimate. No Campaign totals are added to these Contact counts.

Refine the test before making a bigger bet.

The Segment has some encouraging responses, but the evidence does not settle the question. You decide what would be useful to learn next.

Illustrative founder decision
“Continue this test. Find out why four prospects did not see enough value.”

Basis: mixed recorded outcomes and uncertainty about urgency—not an automatic pass or fail.

Next question: Is the barrier the problem itself, the proposed approach, or the effort of switching?

You choose the follow-up and schedule the work. Gadarum does not automatically confirm a customer profile or move the Venture to Launch.

Fictional data and a simplified presentation—not a live test or an exact application screenshot. The two methods show separate illustrative tests; their results must not be combined.

A signal is not a verdictA notebook of source observations and a magnifying glass distinguish a positive follow-up from an unanswered pricing question. The illustration shows why context matters. WHAT HAPPENED? RECORDED SIGNAL Asked for a follow-up. STILL UNANSWERED Would they pay for it? A SIGNAL. NOT A VERDICT.

Useful learning. Not false confidence.

A positive reply isn’t a purchase.
A small sample isn’t a market.

A useful test tells you what happened—and what you still don’t know. Gadarum helps keep the context visible so you can judge how much weight to give a signal.

See the counts and limitations alongside the pattern.

Keep Group and Segment evidence distinct.

Make room for negative responses and unanswered questions.

Inspect the example’s evidence

The power is in the connection

Don’t leave the learning
at the end of the test.

Market Validation captures the work and its outcomes. Venture Health helps you interpret the picture. You choose a response—and Today's Mission helps keep the next work in focus.

Market Validation

Test and capture.

Keep your audience, customer work, and recorded outcomes connected.

Venture Health

Understand it.

Review what looks promising, what conflicts, and what remains unknown.

You, the founder

Make the call.

Decide whether to continue, refine the question, or explore another direction.

Today's Mission

Focus on the work.

Bring your scheduled follow-ups and other commitments into your daily focus.

Powered by the Gadarum Engine. Connected evidence, learning, decisions, and action—with you in control.

A few straight answers

Test the assumptions.
Keep the judgment.

No magic market verdict. A clearer, more disciplined way to learn from real people.

What is market validation?

Market validation is the work of testing assumptions about a customer, their problem, and their response to your proposed solution. In Gadarum, that means defining an audience, doing real customer work, recording outcomes, and reviewing what the evidence supports.

Should I start with a Segment or a Group?

Choose Segment Validation when you have a specific customer profile to test. Choose Group Validation when you want to explore a mixed set of Contacts and compare which profiles respond. A Group is founder-curated; it does not need one shared profile.

Do I need customers or a product before I start?

No. You can begin with prospects and a problem or product idea. Add or import Contacts you intend to learn from. You do not need to record Product Feedback before doing customer validation, and Gadarum does not supply a guaranteed list of buyers.

Can I validate with existing customers?

Yes. Existing customers can help you investigate unmet needs and possible improvements. Keep that audience clear: interest from current customers is not automatically evidence of demand among new prospects.

Does Gadarum send campaigns or run ads for me?

No. Campaigns organize the audience, objective, message, offer, activity plan, and recorded results. Activating Campaign tracking is not the same as sending emails or publishing advertisements. You execute outreach through your chosen channels.

Will Gadarum tell me that my market is validated?

It helps you review evidence, patterns, contradictions, and limitations. It does not automatically certify demand or product-market fit. You decide which customer profile to pursue and whether the available evidence justifies your next move.

How does Market Validation connect to Venture Health?

Market Validation keeps customer testing and its outcomes connected. Venture Health provides the wider interpretation alongside relevant customer, Campaign, Group, Segment, and Product evidence. Today's Mission has a different job: helping you focus on the work. Sources, interpretations, and founder decisions remain distinct.

Put your assumptions
to the test.

Choose an audience. Capture real responses.
Decide where to go next.

Explore the validation example Choose your starting point
Gadarum.

Product · MVP and beyond

Build whatmatters.Learn whatworks.

From a minimum viable product (MVP) to a live offering, connect your features, pricing, and customer feedback to the decisions behind your next move.

See how Product worksFollow the learning loop

Your product. Your decisions. Customer learning in the loop.

From a feature to a better next questionA product feature addresses a customer problem. A customer reports useful results and a sharing blocker. The founder chooses to test an improvement. An arrow carries the next learning back to the product. Illustrative, not a product screen. BUILD → LISTEN → LEARN → IMPROVE A FEATURE WITH A PURPOSEShareable weekly reportCustomer problem“Client updates take too much time.”Expected benefit · not proof CUSTOMER FEEDBACK“Useful report. I still can’tshare it with my client.” FOUNDER DECISIONTest sharing before adding more.THE NEXT TEST BRINGS NEW EVIDENCE
Concept illustration—not a live product screen.
Features tied to needs
Feedback with context
Learning into action

Shipping is progress.
It isn’t proof of value.

Market Validation asks: Who has the problem?
Product adds the next question: Does what we’re building actually help them?

Gadarum connects the solution you intend to deliver with what customers report—so the next product decision has more behind it than a completed task.

How Product works

Give every feature a purpose.
Give every response a place.

Keep the product, the customer problem, and the feedback connected. Not in three separate conversations.

Connect a customer problem to a featureA customer problem card connects to a feature card and an expected customer benefit. A benefit is a hypothesis to test, not validated value. CUSTOMER PROBLEMToo much busywork. A useful featureExpected benefitDEFINE THE VALUE YOU WANT TO TEST
01 / Define the solution

What are you building?
And for whom?

Use the Product overview for context. Describe Features through the customer problem, expected benefit, and relevant market Segment.

Keep the work visible
Track Feature delivery and version labels without calling a completed feature validated.
Why it matters
The feature has a customer purpose you can test—not just a place on a backlog.
Keep feedback connected to a customerA Contact card is connected to a customer report. Source, result and blocker stay attached to the feedback rather than becoming anonymous feature requests. REPORTED FEEDBACK“Useful, but…” Blocker notedTHE CUSTOMER AND THE CONTEXT STAY ATTACHED
02 / Capture the response

What happened when
someone tried it?

Record Product Feedback from the relevant Contact. Capture the source, reported result, blockers, and other required answers. Link the affected Features.

Keep the context attached
Review the customer, feedback, and Feature connection together rather than collecting anonymous requests.
Why it matters
A positive comment and a blocked customer tell different stories. Both deserve a place.
See useful results and unresolved blockersThree feedback records show useful results, a blocker, and a missing answer. The illustration distinguishes evidence from a popularity vote. WHAT ARE WE LEARNING? Useful result reportedSharing is still blockedRepeat use is unknownUNDERSTAND THE SIGNAL. KEEP THE LIMITS.
03 / Review what you learn

What is helping?
What is getting in the way?

Review the Product Snapshot, Feature-linked feedback, and Product Blockers. Follow up on reported friction and carry the evidence into the wider Venture review.

Keep the decision yours
Use the observations to decide what to investigate, improve, or test again.
Why it matters
Customer learning can inform development instead of arriving after the roadmap is already fixed.
One product reference—not a second copy of your business.

The overview uses your Venture description from Settings. Product stage, Features, pricing, and feedback retain their own roles.

See it in context

Feedback is optional. When you add it, the required answers preserve useful context. No feedback does not mean the product has failed.

Keep the tested terms and the customer response togetherA fictional pricing version proposes 29 dollars per month and is later retired. Another version is current at 39 dollars per month. A reported pricing question is linked to the terms discussed. Current does not mean accepted or paid. VERSION 1$29 / monthRetired VERSION 2$39 / monthWritten terms + linked observationsCurrent CUSTOMER QUESTION“Is client sharing included?”ILLUSTRATIVE TERMS · NOT A GADARUM SUBSCRIPTION
Illustrative pricing history and customer observation.

Pricing belongs in the learning

Remember the offer.
Understand the response.

A reaction to “the product” can depend on the price and terms presented. Keep those terms visible instead of overwriting yesterday’s price and losing the context.

Save written pricing terms with Proposed, Current, or Retired states.
Preserve pricing versions and associate relevant customer evidence.
Distinguish your selected price from what customers actually reported.

Current does not mean accepted, signed, or paid. Pricing records support your decision. They do not calculate an optimal price or replace customer billing.

Powered by the Gadarum Engine

Your product is part of the loop.
Not the end of it.

Without customer feedback, a feature is still a hypothesis. Without a next decision, feedback is just a record. Product connects the two inside Gadarum’s wider learning-and-execution loop.

Build, listen, learn and return to the productFeature definition and customer feedback are joined by an iterative path. A founder decision returns learning to the next test. The product is connected to the wider Gadarum loop. FEATURE FEEDBACK LearnBETTER QUESTIONS. BETTER NEXT TESTS.
  1. 01 / Direction

    Choose the problem

    Market Validation helps define who you are learning from and what to test.

  2. 02 / Product

    Make value testable

    Connect a feature to the problem, intended benefit, and relevant audience.

  3. 03 / Interaction

    Do the customer work

    Put the product in front of people through your own tests and conversations.

  4. 04 / Evidence

    Capture what happens

    Record Product Feedback, reported results, and blockers with customer context.

  5. 05 / Learning

    Review the meaning

    Venture Health helps interpret Feature-linked feedback alongside other evidence.

  6. 06 / Decision

    Choose the next move

    You decide whether to refine the product, revisit the audience, or test again.

Next action → next customer test → new evidence.The founder chooses the direction. The loop continues.
Product keeps the solution in view.

What you offer, what you are building, and what customers report.

Venture Health interprets the evidence.

Feature-linked feedback contributes to the broader Venture picture.

Today's Mission brings work into focus.

Scheduled customer follow-ups and evidence reviews can become the next focus.

Venture Memory carries recorded evidence and decision context forward. It does not turn your product description into proof.

One feature. A complete learning loop.

From “we should build this”
to a better next decision.

Follow a fictional weekly reporting feature through five steps. The lesson is the connection—not the screen layout.

01 / Define the hypothesisILLUSTRATIVE WALKTHROUGH

Start with the value. Not the feature count.

A founder is building a weekly reporting tool for independent consultants. Before adding another feature, they make the customer problem and expected benefit explicit.

The founder’s question

Will a shareable report reduce the work of sending client updates?

PRODUCT / FEATURE CONTEXT

Shareable weekly report

Customer problem
Consultants spend too much time assembling and sending client updates.
Expected benefit
Prepare the update once and share it with the client.
Audience hypothesis
Independent consultants managing several client projects.
Founder hypothesis · not customer evidence
Why it matters: Product makes the intended customer value explicit. Writing the benefit does not prove that customers receive it.
02 / Test with customersILLUSTRATIVE WALKTHROUGH

Put the feature in front of real people.

The founder arranges three customer tests through their normal outreach and follow-up work. The customers try the product outside Gadarum; the founder then records what happened.

The founder’s question

Can each customer complete the job—and what gets in the way?

CUSTOMER WORK / TEST PLAN

Watch the job, not just the reaction.

01

Try a real client update

Ask the customer to prepare and share an actual weekly report.

02

Ask about the result

What helped? What was difficult? What still required a workaround?

03

Record the response

Capture feedback on the Contact and link the relevant Feature.

Illustrative founder-run test. Gadarum is not recording sessions or measuring product usage here.

Why it matters: Contact work creates the opportunity to learn. A scheduled test is not a completed result.
03 / Capture customer feedbackILLUSTRATIVE WALKTHROUGH

Keep the useful—and the uncomfortable.

The founder records one useful result and two sharing blockers. Each observation stays connected to its customer and the feature being discussed.

The founder’s question

What did the customer actually report, and what do we still not know?

PRODUCT FEEDBACK / FICTIONAL RECORDS
Contact A · feedback 01Useful result

“Preparing the update was easier than my old document.”

Inspect source context

Source: founder-recorded customer test feedback. Feature: Shareable weekly report. Occurred: September 8, 2026. Payment and repeat use: unknown. Fictional example.

Contact B · feedback 02Blocker reported

“The report is useful, but I still have to copy it into an email.”

Inspect source context

Source: founder-recorded follow-up call. Feature: Shareable weekly report. Occurred: September 9, 2026. Sharing blocker: reported. Payment and repeat use: unknown. Fictional example.

Contact C · feedback 03Blocker reported

“I need a link my client can open.”

Inspect source context

Source: founder-recorded customer message. Feature: Shareable weekly report. Occurrence date: not supplied. Sharing blocker: reported. Payment and repeat use: unknown. Fictional example.

These are three illustrative records, not testimonials or production results.

Why it matters: Product Feedback captures observations and source context. Positive comments, blockers, and unknowns remain distinct.
04 / Review the evidenceILLUSTRATIVE WALKTHROUGH

A useful pattern. Not a market verdict.

Product brings the feedback and blockers into view. Venture Health can interpret Feature-linked feedback alongside other available evidence. The founder reviews the sources before choosing a direction.

The founder’s question

Does the product deliver the promised value all the way through the customer’s job?

ILLUSTRATIVE EVIDENCE REVIEW

Sharing deserves another test.

Some value is reported

Contact A said preparing the update was easier.

A blocker appears twice

Contacts B and C both reported a problem sharing the result.

Important questions remain

Payment and repeat use are unknown. One occurrence date is missing.

Three feedback records are a reason to investigate—not proof of broad demand, retention, or product-market fit.

Why it matters: Venture Health owns interpretation. Product supplies feature context and customer feedback—not a self-awarded success score.
05 / Decide the next moveILLUSTRATIVE WALKTHROUGH

Improve the next test. Then learn again.

The founder chooses to test a sharing improvement before expanding the feature set. They record the decision and arrange customer follow-up rather than treating the interpretation as an automatic instruction.

The founder’s question

What is the smallest next step that could resolve the question?

FOUNDER DECISION / FOLLOW-THROUGH

Test client sharing before adding more.

01

Choose the product change

Build or refine the sharing behavior in your normal development tools.

02

Schedule customer follow-up

Create ordinary Contact Todos. Today's Mission can surface them alongside other commitments.

03

Capture the next result

Did the change remove the blocker? Record the new feedback and review again.

Founder chooses · no automatic product change
Why it matters: The loop returns to action. Recorded decisions preserve the basis; new customer feedback gives you something fresh to learn from.
Step 1 of 5

Interactive illustration only. Contacts, feedback, pricing, and decisions are fictional. Nothing is saved or changed in your Venture.

Beyond the MVP

Your product evolves.
The questions keep coming.

Use Product for a prototype, a minimum viable product, or a live offering. Choose the stage that describes what you have—not the confidence you hope to have.

PRODUCT STAGE

Prototype

Make the proposed solution concrete. Keep the problem and Feature hypotheses visible as you explore what customers understand and need.

PRODUCT STAGE

Minimum viable product

Test an initial usable offering. Capture reported value, friction, and blockers so the next iteration has a learning goal.

PRODUCT STAGE

Live Product

Keep your current offering, pricing, and ongoing feedback connected. New Features still introduce questions worth testing.

Product stage ≠ Feature completion ≠ Venture phase. You can validate a new Feature in a live product. None of these labels automatically proves demand or changes your Validate, Launch, or Grow phase.

A few straight answers

A clearer product.
Not false certainty.

Gadarum supports customer-informed decisions. It doesn’t manufacture product-market fit or make the roadmap for you.

Is this only for an MVP?

No. A minimum viable product (MVP) is one stage—not the whole journey. Product also supports a prototype or a live offering. Keep the relevant features, pricing, and customer feedback together as the product changes.

Does Gadarum build the product for me?

No. Gadarum helps you describe what you are building, connect features to customer problems, and learn from customer feedback. It does not write your product code or replace your engineering tools.

Where do I record Product Feedback?

Start from the relevant Contact. Record the feedback, its source, the reported result, any blocker, and the other required answers. Link the relevant Features when selectable Features exist. Product and the feedback-review workspace bring those records together for review.

Do I need feedback before I can use Product?

No. Feedback is optional. You can use Product stage, Features, and pricing without it. When you do add a feedback record, its required fields preserve useful context. Missing feedback is a knowledge gap, not a reason to block the rest of your work.

Will Gadarum decide which feature to build or what to charge?

No. Product records and evidence support your judgment; they do not automatically rank your roadmap or select the best price. Current pricing is the version you have selected—not proof that customers accepted or paid it.

Does positive feedback prove product-market fit or retention?

No. A useful result is an observation, not proof of a whole market. A stated intention to use the product again is not measured retention. Dedicated product-usage and retention analytics are outside this Product workflow.

Does completing a feature move my venture to Launch?

No. Feature delivery, Product stage, and Venture phase answer different questions. You control the Venture phase separately. A completed feature or a Live Product label does not certify readiness, demand, or commercial success.

Don’t just add another feature.
Close the next learning loop.

Connect what you build to the customer problem, the response, and the decision that follows.

Explore the exampleSee Product in the loop
Gadarum.

Venture Health · Powered by the Gadarum Engine

Know where yourventure stands.And why.

See what customer, market, and product evidence is telling you. Understand the strengths, conflicts, and gaps—so your next decision has a clearer basis.

See Venture Health in action How it works

Not a verdict on your venture. A clearer basis for your judgment.

A clearer picture of your venture, grounded in evidence Illustrative concept, not an app screenshot. Customer outcomes, Campaign results and Product Feedback connect to Venture Health. The example picture includes strengthening customer response, conflicting product signals and missing commercial evidence. These are distinct observations, not an overall score or a launch verdict. EVIDENCE, IN PERSPECTIVE Customers Campaigns Product Venture Health Example THE CURRENT PICTURE A promising direction. Still questions to answer. Customer response Strengthening Product signals Conflicting Commercial evidence Missing NOT AN OVERALL SCORE A clearer basis for your decision. Evidence first.Your judgment, always. Illustrative concept · Not a live product screen
Evidence, not just activity
See the basis behind the picture
Your venture. Your decisions.

Busy doesn’t always
mean making progress.

You have conversations, Campaign results, and product feedback. Some are encouraging. Others raise questions. Looking at them separately makes it harder to see what they mean together.

Venture Health brings the evidence into perspective—so you can distinguish a promising direction from an assumption that still needs testing.

Understand the picture, not just the numbers

Three questions.
A more useful review.

A venture can have encouraging signals and unresolved risks at the same time. One overall score would hide that distinction.

What is strengthening?

Where is the evidence becoming more encouraging?

Look at repeated customer responses, meaningful Campaign outcomes, and Feature-linked feedback—not activity totals alone.

What is conflicting?

Which signals challenge the story you are telling yourself?

Review objections and inconsistent observations alongside the positives. A good signal should not erase a difficult question.

What is still unknown?

Where do you need more evidence before drawing a conclusion?

Keep small samples, missing observations, and uncertain context visible. Not knowing is different from receiving a negative result.

These are ways to understand the evidence—not grades, guarantees, or automatic decisions.

From scattered signals to a clearer picture

Interest is a start.
What does it actually tell you?

Explore a fictional founder’s customer test. See the encouraging signal, the tension, the gaps, and the records behind them.

Venture Health / customer testIllustrative only

A customer profile worth investigating.

In this fictional Group test, operations managers recorded more positive responses than company owners. That is a clue for further exploration—not a proven market.

Operations managers

10people

6 positive · 3 negative · 1 neutral

Company owners

8people

2 positive · 4 negative · 2 neutral

18 people with recorded outcomes. One latest outcome per person. These are counts, not a statistical estimate of market demand.

Promising is not the same as proven.The sample is small. Positive responses do not establish willingness to pay or product-market fit.

A positive response can still contain an objection.

Two reported observations from the same fictional Contact. Interest in trying a product does not mean the barrier to adoption has disappeared.

Encouraging observation

“I’d try this with our operations team.”
Operations manager · Reported customer note

Unresolved concern

“We need a data export before we can try it.”
Same Contact · Reported customer note

Read together: there is reported interest, but product fit is still conditional. These notes do not establish a commitment or a completed trial.

What the evidence cannot tell you. Yet.

An honest review also makes room for unanswered questions. In this example, three important limits remain.

Product usefulness is still untested here.

No Feature-linked Product Feedback has been recorded. An invitation to try the product is not evidence of using it.

The sample covers a narrow audience.

These 18 Contacts are an exploratory Group, not a representative sample of the whole market.

Some observation dates are unknown.

A note’s recording date does not necessarily tell you when the conversation happened.

Missing evidence is not a failed test. It limits how much you can conclude.

Open the basis. Make your own call.

An interpretation is more useful when you can inspect the records behind it. Open these fictional examples to see the distinction.

Group test: recorded customer outcomes18 people · An exploratory comparison

Invented example record

Operations managers: 6 positive, 3 negative, 1 neutral.
Company owners: 2 positive, 4 negative, 2 neutral.

Each person contributes one latest recorded outcome. Profile labels reflect current Contact details; they are not reconstructed historical attributes.

Limit: this descriptive comparison does not establish statistical significance, market demand, or a confirmed ideal customer profile.

Customer note: interest with a conditionReported observation · Occurrence date unknown

Invented example record

“I’d try this with our operations team. We need a data export before we can try it.”

Source: a founder-recorded note linked to an operations manager in the example Group. The actual conversation date is unknown.

Limit: this is a reported statement—not a signed agreement, product-use record, or independently verified fact.

Possible founder decision: test the conditionIllustrative choice · Not made by Gadarum

Illustrative founder choice

“Continue exploring operations teams, and investigate whether the data-export requirement is shared by other prospects.”

Basis: the small Group comparison and the reported adoption concern.

Boundary: this does not confirm the market or automatically schedule any work. The founder chooses and records the response.

Sources, interpretations, and founder decisions play different roles. One should not silently replace another.

Fictional data and a simplified presentation—not a live dashboard or an exact application screenshot. Illustrates Group analysis, recorded observations, evidence limitations, and founder review.

The connected view

One venture.
More than one kind of evidence.

Each part of your venture answers a different question. Venture Health helps you review the parts without losing the bigger picture.

Customer profiles connected to different response signals
Customer & market evidence

Are you reaching
the right people?

Review Segment response patterns and your confirmed ideal customer profile, with its recorded decision basis and relevant limitations.

A Campaign result stays connected to its audience and context RESULT + CONTEXT
Campaign evidence

Is the activity
telling you anything?

Distinguish work still in progress from meaningful, weak, or inconclusive results. Keep each Campaign’s audience and context in view.

Product Features connected to customer feedback and blockers
Product evidence

Is the product
addressing the need?

Connect Feature-linked customer feedback to the product picture, including reported benefits and blockers—not just what has been built.

Explore emerging customer patterns.

Group Validation keeps exploratory audience learning visible, with sample sizes and caveats.

Review competing signals.

Learning and Conflict records help you examine observations that do not fit a simple story.

Consider the evidence before Launch.

A dedicated Validate-to-Launch review surfaces relevant evidence and gaps. It does not certify readiness.

Follow the interpretation back to its sourceOriginal records, interpretation and your decision stay distinct. A magnifying glass highlights a recorded customer observation rather than replacing it with a generated conclusion. ORIGINAL CUSTOMER RECORD “We need a way to exportour data before we can try it.” Reported observation · Not a verdict Source context and known limitations See the source. Understand the context.

A conclusion should come with a reason

See the source.
Keep the context.

A summary is a starting point—not a substitute for the evidence. Follow available source links, review what was recorded, and understand the limitations before drawing your own conclusion.

A customer observation is not a generated conclusion.

A recorded decision is not new customer evidence.

An unknown date or small sample still matters.

Inspect the example sources

One connected system. Clear responsibilities.

Understand it in Venture Health.
Put your decision to work in Today's Mission.

The Gadarum Engine connects the learning loop. Venture Health explains the picture; you choose your response; Today's Mission gives the work a place to happen.

Venture Health

Understand the situation.

Review the evidence, its meaning, and what remains uncertain.

You, the founder

Choose your response.

Decide what to continue, change, or investigate. Record your reasoning.

Today's Mission

Focus on the work.

Bring scheduled commitments, reviews, and decision follow-ups into focus.

Venture Memory connects source records, important history, and recorded decision context across the loop.

A few straight answers

Useful perspective.
Not false certainty.

Venture Health helps you understand what you have learned—and where you still need to learn more.

What is Venture Health?

Venture Health is Gadarum’s evidence-interpretation view. It brings together customer, Segment, Campaign, Group, and Product evidence so you can review the current picture, its supporting context, and unresolved questions. It does not replace the original records or your judgment.

How is this different from an activity dashboard?

An activity dashboard can show what happened or how much work was done. Venture Health adds interpretation: whether recorded signals are meaningful, strengthening, weakening, conflicting, or inconclusive. A higher activity count is not automatically better evidence.

Does Venture Health give my business a score?

No universal health or survival score. Different evidence can point in different directions. Customer interest may look encouraging while product usefulness or commercial commitment remains uncertain. Those distinctions should stay visible rather than collapse into one number.

Will it tell me that I am ready to launch?

The dedicated Validate-to-Launch assessment helps you review relevant evidence, contradictions, and gaps while you are in Validate. It does not certify readiness, declare product-market fit, or change your Venture phase. The decision to launch remains yours.

What happens when I have little or incomplete evidence?

You can still organize your venture and do customer work. The interpretation should reflect the limits of what has been recorded. A small sample, missing feedback, or unknown timing is a reason for caution—not a negative result or a confident conclusion.

Does it verify sales or measure customer retention?

Recorded commercial outcomes are evidence you capture, not independent payment verification. An isolated “I would use it again” response is not retention history. Venture Health does not independently verify sales or provide complete retention and growth analytics.

Less guessing.
A clearer picture.

Know what your evidence supports, what it challenges,
and what you still need to understand.

Explore Venture Health Revisit the three questions
Gadarum.

The Gadarum Engine

Customer evidence.Clearer decisions.Your next move.

Connect what customers say and do with the decisions you make and the work you do next. One learning loop, powered by your venture’s real context.

See the engine in action How it works

You decide. Gadarum helps you see why.

Customer learning, connected to your next move Customer conversations, market tests, and product feedback flow into the Gadarum Engine. You review the learning and choose your next action. The next action leads back into further customer learning. A CONNECTED LEARNING LOOP Customerconversations Market testsCampaigns & outcomes Product feedbackBenefits & blockers GADARUMENGINE Your review. Your call. YOUR NEXT MOVE A more focused test. Chosen by you. Connected to the evidence. LEARN. DECIDE. ACT. REPEAT.
Connected customer context
Evidence before assumptions
Founder-led decisions

You have information.
You need direction.

A customer conversation. A Campaign result. A feature request. Each tells part of the story. But what do they mean together—and what should you do about them?

The Gadarum Engine connects the records you capture so customer learning can inform your next decision, not just sit in another report.

How the engine works

One connected loop.
Each step has a job.

Customer work creates evidence. Evidence informs learning. You choose the next move—and the learning continues.

  1. 01 / DIRECTION

    Choose a question.

    Define the customer, problem, or assumption you want to test.

  2. 02 / ACTION

    Do the real work.

    Talk to customers, run a market test, or gather product feedback.

  3. 03 / EVIDENCE

    Record what happens.

    Keep outcomes connected to their source, audience, and available context.

  4. 04 / LEARNING

    Review the meaning.

    Examine patterns, conflicts, gaps, and suggestions against the evidence.

  5. 05 / DECISION

    Make your call.

    Choose what to continue, change, or investigate. Record the basis for it.

  6. 06 / NEXT ACTION

    Put learning to work.

    Plan the next customer activity. Its outcome gives you more to learn from.

Connected by Venture Memory

Source records, important history, and recorded decision context give the next review a starting point.

From insight to a next move

What does that look like
in practice?

Follow a market-validation example.
Illustrative data and diagrams—not live results or product screenshots.

Market validation / exampleIllustrative only

The starting point is customer reality.

You’re exploring a workflow tool with a mixed Group of prospects. You capture their responses and the context behind them.

“Our weekly handoffs are a mess.”

Operations manager · reported customer pain
Customer note

Asked to see how the workflow would fit.

Operations manager · recorded positive outcome
Follow-up

“This isn’t a priority for us right now.”

Company owner · recorded objection
Customer note

Reported observations are useful context. They are not independently verified demand.

A promising pattern. Not proof.

Group analysis compares recorded outcomes by customer profile. The sample and its limitations stay visible.

Counts include Contacts with positive or negative recorded outcomes. Neutral and untested Contacts are not in these denominators.

A clue worth another test. This small exploratory sample does not establish demand, a winning market, or product-market fit.

The decision is yours to make.

A suggested customer profile is an option to review. It does not become a validated market just because it was suggested.

Illustrative founder decision

“Test the operations-manager profile in a more focused follow-up.”

Basis for the decision

Stronger observed response in the exploratory Group.

Still unknown

Whether the pattern holds and the problem is urgent enough.

Keep the reasoning connected to its reviewed evidence and limitations.

Now the learning has somewhere to go.

You schedule the next customer work. Today's Mission gives that work a place in your focus, alongside your existing commitments.

Founder-scheduled work
Follow up with three
operations managers.
What you want to learnHow urgent is the problem? What do they use today? What would make them consider a change?

Record what happens. Bring the new evidence into the next review.

The power is in the connection

Understand it. Remember why. Act.

Three complementary roles.
One continuous founder workflow.

Venture Health brings supporting, conflicting, and missing evidence into view THE EVIDENCE PICTURE Supporting signals Conflicting evidence Open questions
Venture Health

See what the
evidence is saying.

Review customer, market, and product signals together—including conflicts, weak evidence, and questions that remain open.

Venture Memory connects evidence, a founder decision, and its recorded reasoning EVIDENCE YOUR DECISIONThe recorded why.
Venture Memory

Keep the why
behind the decision.

Retain important source records, history, and decision context so you can revisit what informed your direction.

Today's Mission turns a long field of possibilities into one primary focus ONE PRIMARY FOCUS Your next customerconversation.
Today's Mission

Give the next step
a place to happen.

Bring scheduled commitments, evidence reviews, recommendations, and decision follow-ups into one primary focus.

The founder stays at the center of the decisionEvidence and analysis inform the founder. Possible directions branch outward, but the founder chooses the next move. A possible path Your next move Another option YOU DECIDE

Your judgment stays in charge

AI helps you think.
It doesn’t take the wheel.

Gadarum combines AI-assisted analysis with rule-based interpretation and prioritization. It helps surface what deserves a closer look—not automatically choose your market, set your price, or declare you ready to launch.

Sources stay visible.Uncertainty stays explicit.The decision stays yours.

A few straight answers

What the engine is.
And what it isn’t.

No black-box promises.
Just a clearer way to work with what you know.

What is the Gadarum Engine?

The Gadarum Engine is the connected learning-and-execution approach behind the product. It brings recorded customer activity, evidence, interpretation, founder decisions, and next actions into one workflow. It is not a separate product you have to configure.

Is it just an AI chatbot?

No. The value is in how your customer records and workflows connect. AI can help analyze and summarize, while rules support interpretation and prioritization. Venture Health, Venture Memory, and Today's Mission each play a different role.

Does it tell me that my market is validated?

No. Patterns and recommendations help you evaluate a market; they do not certify demand or product-market fit. You review the evidence, its source, and its limitations, then make the decision yourself.

Does it automatically collect every interaction?

No. You capture or import supported records. The Engine works with that recorded context. It does not imply automatic email syncing, independently verified payments, or autonomous outreach.

What happens when I don’t have enough evidence?

You can still define your direction, organize Contacts, and plan customer work. But missing or inconclusive evidence should remain a visible gap—not turn into a confident claim. The next useful step may be to learn more.

Let customer learning
lead somewhere.

From the question you test to the move you choose next,
keep the evidence and the work connected.

Explore the example Revisit the learning loop
Skip to questions
Gadarum.

Frequently asked questions

Your questions.
Straight answers.

Get to know how Gadarum works, what it helps you do, and where you stay in control. All the answers, organized by topic.

37 questions & answers6 topics

About Gadarum

Explore this topic
What is Gadarum?

Gadarum is a connected workspace for founders to organize market tests, customer records, Product Feedback, evidence reviews, and decisions. Its purpose is to connect what you learn from customers with what you do next.

Who is it for?

Founders testing a business idea or developing an existing product. You can start with a customer hypothesis or bring the Contacts you already have. You do not have to be a technical founder to work through these questions.

Is this another AI chatbot or task manager?

The main value is the connection between customer evidence and execution. AI can help analyze; rules support interpretation and prioritization. Venture Health explains the evidence, while Today's Mission focuses the work. You remain responsible for strategic decisions.

Can I bring my existing customer information?

The documented workflows support Contact CSV import and a separate historical Notes import into existing Contacts. This is not a promise of complete CRM migration, automatic email history, or importing every type of customer record.

Will Gadarum tell me I’ve found product-market fit?

No. It helps you examine customer signals, conflicting evidence, sample limitations, and open questions. A positive response or a suggested Segment is not proof of demand. You decide what the evidence justifies.

Does Gadarum run campaigns or build the product for me?

No. It helps you define, organize, and review the work. You carry out customer outreach and build your product using the appropriate tools. Gadarum connects the recorded outcomes back to learning and decisions.

Validate. Launch. Grow.

Explore this topic
Do I have to start in Validate?

No. You can bring an existing venture and explicitly choose its phase in Settings. Prior learning can inform your starting context; entering Launch does not mean Gadarum conducted or certified your earlier validation.

Can I keep validating after I launch?

Yes. You can test a new audience, message, offer, or product assumption while the venture is in Launch. Validation is ongoing work, not a stage you are forbidden to revisit. Changing the venture phase is a separate founder decision.

Does a finished product mean the venture is ready to launch?

No. Product stage, feature delivery, and venture phase describe different things. A working product does not by itself establish demand, pricing acceptance, or a repeatable way to acquire customers.

Does Gadarum decide when I move to another phase?

No. You explicitly choose the phase. Evidence review can inform your judgment, but no universal score or automatic transition makes the strategic decision for you. Selecting a phase is not proof that its business goals have been achieved.

Is Grow a full growth-analytics product today?

Not yet. The shared venture workspace and Grow phase are part of the foundation. Dedicated retention, churn, repeat-purchase, and repeatability analysis are planned extensions, not capabilities this page presents as available.

What happens to my learning if I change direction?

Existing customer records, evidence, and recorded decisions remain in the venture when you change its phase. Earlier findings keep their original context; changing a phase does not turn an old assumption into newly validated evidence.

Market Validation

Explore this topic
What is market validation?

Market validation is the work of testing assumptions about a customer, their problem, and their response to your proposed solution. In Gadarum, that means defining an audience, doing real customer work, recording outcomes, and reviewing what the evidence supports.

Should I start with a Segment or a Group?

Choose Segment Validation when you have a specific customer profile to test. Choose Group Validation when you want to explore a mixed set of Contacts and compare which profiles respond. A Group is founder-curated; it does not need one shared profile.

Do I need customers or a product before I start?

No. You can begin with prospects and a problem or product idea. Add or import Contacts you intend to learn from. You do not need to record Product Feedback before doing customer validation, and Gadarum does not supply a guaranteed list of buyers.

Can I validate with existing customers?

Yes. Existing customers can help you investigate unmet needs and possible improvements. Keep that audience clear: interest from current customers is not automatically evidence of demand among new prospects.

Does Gadarum send campaigns or run ads for me?

No. Campaigns organize the audience, objective, message, offer, activity plan, and recorded results. Activating Campaign tracking is not the same as sending emails or publishing advertisements. You execute outreach through your chosen channels.

Will Gadarum tell me that my market is validated?

It helps you review evidence, patterns, contradictions, and limitations. It does not automatically certify demand or product-market fit. You decide which customer profile to pursue and whether the available evidence justifies your next move.

How does Market Validation connect to Venture Health?

Market Validation keeps customer testing and its outcomes connected. Venture Health provides the wider interpretation alongside relevant customer, Campaign, Group, Segment, and Product evidence. Today's Mission has a different job: helping you focus on the work. Sources, interpretations, and founder decisions remain distinct.

Product & MVP

Explore this topic
Is this only for an MVP?

No. A minimum viable product (MVP) is one stage—not the whole journey. Product also supports a prototype or a live offering. Keep the relevant features, pricing, and customer feedback together as the product changes.

Does Gadarum build the product for me?

No. Gadarum helps you describe what you are building, connect features to customer problems, and learn from customer feedback. It does not write your product code or replace your engineering tools.

Where do I record Product Feedback?

Start from the relevant Contact. Record the feedback, its source, the reported result, any blocker, and the other required answers. Link the relevant Features when selectable Features exist. Product and the feedback-review workspace bring those records together for review.

Do I need feedback before I can use Product?

No. Feedback is optional. You can use Product stage, Features, and pricing without it. When you do add a feedback record, its required fields preserve useful context. Missing feedback is a knowledge gap, not a reason to block the rest of your work.

Will Gadarum decide which feature to build or what to charge?

No. Product records and evidence support your judgment; they do not automatically rank your roadmap or select the best price. Current pricing is the version you have selected—not proof that customers accepted or paid it.

Does positive feedback prove product-market fit or retention?

No. A useful result is an observation, not proof of a whole market. A stated intention to use the product again is not measured retention. Dedicated product-usage and retention analytics are outside this Product workflow.

Does completing a feature move my venture to Launch?

No. Feature delivery, Product stage, and Venture phase answer different questions. You control the Venture phase separately. A completed feature or a Live Product label does not certify readiness, demand, or commercial success.

Venture Health

Explore this topic
What is Venture Health?

Venture Health is Gadarum’s evidence-interpretation view. It brings together customer, Segment, Campaign, Group, and Product evidence so you can review the current picture, its supporting context, and unresolved questions. It does not replace the original records or your judgment.

How is this different from an activity dashboard?

An activity dashboard can show what happened or how much work was done. Venture Health adds interpretation: whether recorded signals are meaningful, strengthening, weakening, conflicting, or inconclusive. A higher activity count is not automatically better evidence.

Does Venture Health give my business a score?

No universal health or survival score. Different evidence can point in different directions. Customer interest may look encouraging while product usefulness or commercial commitment remains uncertain. Those distinctions should stay visible rather than collapse into one number.

Will it tell me that I am ready to launch?

The dedicated Validate-to-Launch assessment helps you review relevant evidence, contradictions, and gaps while you are in Validate. It does not certify readiness, declare product-market fit, or change your Venture phase. The decision to launch remains yours.

What happens when I have little or incomplete evidence?

You can still organize your venture and do customer work. The interpretation should reflect the limits of what has been recorded. A small sample, missing feedback, or unknown timing is a reason for caution—not a negative result or a confident conclusion.

Does it verify sales or measure customer retention?

Recorded commercial outcomes are evidence you capture, not independent payment verification. An isolated “I would use it again” response is not retention history. Venture Health does not independently verify sales or provide complete retention and growth analytics.

Gadarum Engine

Explore this topic
What is the Gadarum Engine?

The Gadarum Engine is the connected learning-and-execution approach behind the product. It brings recorded customer activity, evidence, interpretation, founder decisions, and next actions into one workflow. It is not a separate product you have to configure.

Is it just an AI chatbot?

No. The value is in how your customer records and workflows connect. AI can help analyze and summarize, while rules support interpretation and prioritization. Venture Health, Venture Memory, and Today's Mission each play a different role.

Does it tell me that my market is validated?

No. Patterns and recommendations help you evaluate a market; they do not certify demand or product-market fit. You review the evidence, its source, and its limitations, then make the decision yourself.

Does it automatically collect every interaction?

No. You capture or import supported records. The Engine works with that recorded context. It does not imply automatic email syncing, independently verified payments, or autonomous outreach.

What happens when I don’t have enough evidence?

You can still define your direction, organize Contacts, and plan customer work. But missing or inconclusive evidence should remain a visible gap—not turn into a confident claim. The next useful step may be to learn more.

Skip to content
Gadarum.

Join the Gadarum waitlist

Your next move.
With more clarity.

Tell us what you’re building and where you need help. Request early access to find the right customers, test demand, and turn learning into action.

Preview mode

Explore the form and thank-you page. Your information is not sent or saved.

Request early access

Fields marked are required.

0 of 12 complete
You & your venture

A domain such as yourcompany.com is fine.

Where you are today

This is about the venture you are currently building — not your personal job title or profession.

Choose the primary market or industry your venture serves.

What you want to achieve
Stay in the loop

For example, linkedin.com/in/your-name.

Preview only. Consent is not recorded. The final Privacy Policy will be published before signups open.

Preview only · Opens the thank-you page without submitting your information.

Skip to content
Gadarum.

The next chapter starts with a question

Thank you for your
interest in Gadarum.

We’ll share updates about Gadarum and early access soon. In the meantime, explore how customer evidence becomes clearer decisions and focused action.

Confirmation preview

This demonstrates the thank-you page. No request was submitted, no information was saved, and no update has been scheduled.

Explore the Gadarum Engine Back to Home
Skip to content
Gadarum.

Website preview

Privacy Policy

The final Privacy Policy is not published yet.

A placeholder, not a live policy.

This page reserves the Privacy Policy destination in the website preview. It does not contain the final policy and does not record acceptance.

The preview form does not send or save your information. The consent checkbox and thank-you page demonstrate the intended experience only.

The final Privacy Policy must be added and reviewed before the waitlist is opened for real submissions.

Return to the waitlist form