Values-Driven Goal Setting for Founders: A Case Study

Adaeze had been building for three years.

Her SaaS platform — a project management tool for architecture firms — was growing steadily, had a healthy NPS, and was consistently profitable. By every external metric she tracked, the company was succeeding.

She was also deeply, persistently unhappy with it.

This is the case study of what she found when she ran a values audit on her goals — and how it changed not just her roadmap but her entire relationship to the company she’d built.

Baseline: Succeeding at the Wrong Goals

Adaeze’s goal stack at the time of the audit:

• Reach 500 paying customers by end of year
• Raise a seed round to accelerate growth
• Hire a head of sales to reduce her direct involvement in deals
• Launch two new feature modules per quarter

All four goals were reasonable. All four were what a well-advised founder at her stage would be expected to pursue. All four were producing results she didn’t find satisfying.

She’d run values word lists twice — once at the start of the company and once a year later. Both times she’d selected integrity, creativity, and impact. Standard language. Didn’t tell her much.

When she tried the Values Triangulation, the picture became significantly more specific.

Running the Triangulation

What she defended:

Adaeze described three incidents in detail. The first was a pushback against an investor who suggested she simplify the product to broaden the addressable market. She’d been viscerally opposed — the specificity was the point, she’d argued. The second was a heated exchange with her first engineering hire about cutting corners on data visualization. She refused to ship something she considered “dishonest to the data.” The third was declining a partnership with a larger platform that would have tripled her distribution but required branding the product under their name.

Pattern: she defended craft specificity and authorship. Not just quality in the abstract — quality that she could trace back to specific intentional decisions she’d made.

What made her jealous:

She listed four: independent architects who designed one building every few years with total control over every decision; documentary filmmakers whose names were attached to their work; a former colleague who had left enterprise software to teach design at a university; and a product designer at a small agency who wrote publicly about process.

Pattern: traceable authorship, slowness as craft, explaining the thinking as part of the work.

What she would quit over:

Optimizing for usage metrics at the expense of usefulness. Shipping features she didn’t believe in because a large customer requested them. Running a company where the culture was performance rather than practice.

Pattern: quality over velocity, genuine usefulness over surface engagement, cultural coherence.

What the AI Reflected Back

She pasted all three sections into her AI tool with the pattern-extraction prompt.

The output identified four operating values:

1. Attributed craft — the work must be traceable to specific intentional decisions, and those decisions must be hers or made in collaboration with people who share the standard.
2. Slowness as a feature — depth requires time; speed that compromises depth violates something fundamental.
3. Explained process — the thinking behind the work matters as much as the output. She values transparency about method, not just results.
4. Coherence over scale — a smaller, more coherent thing is worth more than a larger, incoherent one.

The AI also flagged a tension: attributed craft and scale have a structural conflict. The larger a company grows, the harder it is to maintain traceable authorship over decisions. The seed round goal pointed toward scale. Her values pointed toward coherence. These were not the same direction.

Version 1 Failure: The Goal Stack as Written

Looking at her four goals through the values lens produced an uncomfortable clarity.

Reach 500 customers: Not inherently misaligned, but the framing was wrong. “500 customers” optimized for count. Her values called for optimizing for depth of usefulness. A goal framed as “500 customers who rely on this for something they couldn’t do without it” would be different in how it shaped daily decisions.

Raise a seed round: Misaligned. The seed round was predicated on a growth trajectory that would require scale-first, coherence-later decisions. Her values didn’t support that ordering. She would spend the money hiring people she’d have to manage away from her standards, moving at a pace that would compromise the craft quality she consistently defended.

Hire a head of sales: Neutral to slightly misaligned. Her value around explained process suggested she was probably the best person to run the sales conversation — because she could explain the product’s reasoning in a way a sales hire couldn’t. This wasn’t about never hiring; it was about not removing herself from the customer relationship at this stage.

Launch two feature modules per quarter: Misaligned. Two modules per quarter was a velocity commitment. Her values were anti-velocity when velocity required compromising depth.

Three of four goals had significant values-misalignment. She hadn’t noticed because they all looked like reasonable founder goals.

The Redesign

Adaeze spent two weeks in a values-goal redesign process. She used AI iteratively — not to generate goals for her, but to check draft goals against her stated values before committing to them.

The prompt she returned to repeatedly:

Here is a goal I'm considering: [goal]

Here are my operating values: [attributed craft, slowness as feature, explained process, coherence over scale]

Is this goal more consistent with my values as stated, or is it more consistent with the conventional expectations of a SaaS founder at my stage?
If there's a tension, describe it specifically.

The distinction — values vs. conventional expectations — proved to be the right question. She discovered that almost all of her original goals were the latter.

Her redesigned goal stack:

• Build 100 customers who use the product for their most complex projects, not their simplest. (Coherence over scale; attributed craft.)
• Write one detailed process explanation per quarter — public, specific, about how a product decision was made. (Explained process.)
• Maintain a 3-month roadmap maximum; decline the seed round and stay profitable at current scale. (Slowness as a feature; coherence over scale.)
• Hire one designer who shares the quality standard rather than a sales function. (Attributed craft; coherence.)

The goals were smaller, more specific, and more coherent with each other than the previous set. She also immediately found them more motivating — not because they were easier, but because they were hers.

Six Months Later

Adaeze didn’t reach 500 customers. She reached 180, and grew revenue by 28% on that smaller base because her target customers were willing to pay significantly more for something that fit their work precisely.

She declined two investor conversations. She said no to a potential enterprise partnership that would have required customization that violated her quality standards.

She also started writing publicly about product decisions — a newsletter with about 1,400 subscribers, mostly architects and designers. The writing itself became a business development channel, though that wasn’t the original intent.

The metric she cares most about now: would she be comfortable explaining every product decision that shipped this quarter in detail, in public? When the answer is yes, the company is running on her values. When it’s no, something has drifted.

What the Case Study Shows

Values-goals misalignment rarely looks like catastrophe. It looks like success you don’t want to talk about. It looks like hitting targets and feeling hollow. It looks like motivational erosion that you blame on burnout when the actual cause is structural.

Adaeze wasn’t burned out. She was building toward something that didn’t match what she actually cared about.

The fix wasn’t a mindset shift. It was a goals redesign — one that required first surfacing the values the original goals were violating, and then building a replacement structure from the values up.

Beyond Time (beyondtime.ai) is designed to help founders maintain this kind of values-goals coherence at the daily planning level — tagging calendar time to values so the gap between what you claim to care about and where you actually put your hours becomes visible without requiring a quarterly audit to catch it.

Action: Look at your current goal stack and ask honestly: are these goals mine, or are they what a well-advised person at my stage is supposed to want?

Related:

• Complete Guide: Personal Values and AI Goal Setting
• The Values-Based Goal Framework with AI
• Beyond Time Values Alignment Walkthrough
• How to Align Goals with Values Using AI
• Complete Guide: Setting Goals with AI

Tags: founder goals, values-driven leadership, case study, goal alignment, AI planning