What It Is

We design the software your business needs as a clickable prototype and plain written requirements, tested with real users before anyone writes code.

Who It's For

Leaders whose teams live in spreadsheets, workarounds and tools that almost fit, and who need something built around how the work really happens.

What Changes

You see, click and approve the software before it’s built, so the build matches what your people need the first time.

This might be you if...

“Our team runs the business out of spreadsheets and email.”

“We bought software that does 80% of what we need, and we work around the rest.”

“Everyone describes the system they want differently.”

“Our last build looked fine in the demo, and nobody used it.”

“I can’t tell whether we need custom software or just better setup.”

“The developers keep asking questions we thought were answered.”

What It Is

Design the software around the work, then build it

Most software problems start before the first line of code. Requirements live in long documents nobody can picture. Screens get designed while the data rules, permissions and error states stay vague, so developers guess.

We design the other way round. We watch how your associates actually work, then turn what we learn into a clickable prototype you can test. Written requirements cover what a screen can’t show: data rules, integrations, security and performance. Together they become plain, testable acceptance criteria. And if an off-the-shelf tool already fits, we’ll say so and integrate it.

How wYrks does it differentlyWe watch before we design.Transformational Anthropology shows us how work really moves, where people re-key data and why tools get abandoned. The design starts from that, not from a feature wish list.You click it before we build it.The prototype is the main reference for how the software behaves. You approve it at a Module Prototype Review, and every change after that is logged with its impact on scope, time and cost.Designed for value, not minimum.We aim for a Value Focused Product: the smallest version that does the job well, accessible and secure from day one, with a roadmap for what comes next.

What the screen shows, and what it doesn’tEvery module we design comes with two halves. The prototype shows what people will see. The written spec covers what they won’t, and that’s usually where projects go wrong.Design runs one module ahead of development, so you’re reviewing the next piece while the current one is being built.Above the waterline · what the prototype showsScreens, flows and content for each key taskWho sees what, by roleLoading, empty, error and offline statesAccessibility in practice: keyboard, contrast, labels (WCAG 2.2 AA target)Microcopy, labels and error messagesBelow the waterline · what the written spec coversData and business rules: validations, calculations, lifecyclesPermissions enforced on the server, not just hidden buttonsIntegration contracts: what goes in, what comes out, what happens on failurePerformance targets and security expectationsWhat’s out of scope, and the assumptions we’re makingBoth halves end in acceptance criteria: plain, testable statements of what “done” means, approved at a Module Prototype Review. Any change after that is logged with its effect on scope, time and cost.

What you get

4P Strategic Evaluation readout

How your leadership and frontline teams each see Purpose, Process, Proof and Promise, side by side, with every answer traced to how people know it.

Challenge Statement and Success Measures

The real problem in one paragraph, plus the human and business measures (HPIs and OKRs) that will show it’s solved.

Why Statement and Mantra

The root reason your organization exists, reduced to a short line people can repeat and act on.

Purpose Statement, tested

One sentence built around your customer, with the decision-test results from your managers.

Desired State Statement

The agreed picture of where you’re going, signed off by your sponsor as the mandate for what follows.

Charter and Next-Step Roadmap

Who does what next, in what order, and how we’ll know it’s working.

Software Charter and use-case inventory

What the software is for, who uses it and how success will be measured.

Journey maps and service blueprint

How work moves today, front stage and back stage, and where it breaks.

Clickable prototype

Every key screen and state, usability-tested with the people who’ll use it.

Requirements Pack, per module

Prototype references, written under-the-hood rules and acceptance criteria.

Design system and accessibility checklist

Reusable components and the standards developers and testers work to.

Phased roadmap

What ships first, what follows, and what each module unlocks.

In our clients’ words · PowerPlay Corp

Scoped by watching the work. Delivered on time and within budget.

The Valadate platform was scoped through Transformational Anthropology sessions and wireframes before build, and completed on time and within budget.

So professional and navigated the process to keep us on track and make a non tech savvy individual feel comfortable and engaged!

Oscar Pedraza

Founder, Valadate

Software DesignThe friction, root causes and technology gaps found in a Friction Audit or systems review, plus agreed success measures.Turns validated concepts into a tested, buildable design, closing capability and technology gaps without adding new friction.An approved prototype and Requirements Pack that meet our Definition of Ready, so development starts without guesswork.Every wYrks service is a building block of I.D.I.D., the path from understanding the parts to aligning the whole.See the full I.D.I.D. processIdentifyClarify the challengeDefineUncover truths & close gapsIdeateConceptual bridgeDeliverRefine, build & executeEvolveSustain, then elevateCommitment Brand

Often Paired With

Before it · Process

Market Research & Probes

Check whether what the market hears matches the purpose you're delivering on.

Explore Market Research & Probes →

Alongside it · Purpose

Brand Audits

Check whether what the market hears matches the purpose your leaders just agreed on.

Explore Brand Audits →

After it · Process

Corporate Culture Alignment

Turn the purpose into daily behavior, incentives and norms across your teams.

Explore Corporate Culture Alignment →

Before it · Purpose

Product & Service Ideation

Turn validated needs into concepts, then test them again.

Explore Product & Service Ideation →

Alongside it · Promise

Communication Strategies

Settle what you’re saying, and to whom, while designing what will be sold.

Explore Communication Strategies →

After it · Process

Expert Software Development

Build the approved design by modules you can see and test.

Explore Expert Software Development →

FAQs

Custom Software Design questions

Do we need custom software at all?

Not always. We start by inventorying what you already run. Where off-the-shelf works, you keep it and we integrate it. We design custom only for the piece that’s missing.

What do you need from us?

Time with the people who do the work, access to the tools and data they use, and a decision-maker for each prototype review. Fast feedback at reviews keeps rework down.

Can design stand alone?

Yes. You leave with a tested prototype and a Requirements Pack any competent team can build from. Most clients have us build it too, because the same team carries the intent through.

How long does it take, and what does it cost?

It depends on the number of modules. We size work from Small to XXL, then estimate each module as a range with a stated confidence level. Ranges tighten as the prototype firms up.

QUALITY DESIGN IS WHERE GREAT SOFTWARE BEGINS