The MMWB Software Workshop

Software that reclaims your focus.

Most software is built around platform logic, not people logic. The Workshop turns a different approach into product concepts and working software.

Inside the Workshop

MaxiMail

Product development
MaxiMail application with relationship groups, attention tools, and smart views alongside the current conversation.
The premise

We start from the person — and work outward until the experience is the kind users cannot imagine going back from.

Six ideas for software with better instincts.

Cognitive overload, context switching, notification fatigue — the frustration is widespread. These concepts are what we want to be using daily, on the platforms millions already rely on.

MaxiMail product-development overview with the application and its advanced communication capabilities.

Building MaxiMail

How Ben Klaiber conceived the product, designed its workflows, and directed AI-assisted development. A detailed account of the product decisions, architectural corrections, and engineering work behind MaxiMail.

Read development case study

MaxiMail

MaxiMail Attachment Workspace with bookmarks, grouped project files, and a document workspace.

AI-assisted writing, rich Snippets with variables, images and GIFs, and an Attachment Workspace for bookmarking, image conversion, and one-click OCR.

Explore MaxiMail
01

Attune. Music that gets the Vibe.

Reaction Intelligence · Signal-Driven Recommendations · Love / Like / Never

Your reactions become the algorithm.

A like in the background while you're cooking isn't the same as a like you stopped to search for.

Open concept →
02

Conduct

Relationship Logic · Time-Aware Tiers · Contact-First Design

Right person.
Right time.

Your relationships are invisible to the system, and your day has no shape it can recognize.

Open concept →
03

Always On Top

Persistent Context · Calm Priority · No Lost Work

Keep context where you need it.

The things that matter should stay present without taking over your whole screen.

Open concept →
04

TrueTeams

8 themes · 25 features · Precision messaging

Knowledge in the flow of work.

The tool that carries your consequential conversations should have clarity, accountability, and memory.

Open concept →
05

Notifications Concept

Context Anchoring · Device Hierarchy · Per-App Budgets

Fewer.
Smarter.
Timely.

Modern notification systems forget what you just handled and force all-or-nothing overload.

Open concept →
Workshop field notes

We don’t start with features.
We start with the friction.

Every Workshop concept begins by watching where existing software breaks the natural flow of work, attention, or decision-making. Then we reduce the problem to its underlying behavior and build outward from there.

01 Observe

See what people are actually doing.

Start with real behavior, not what the software assumes people are doing.

Attune interface detail
02 Reframe

Find the problem underneath the interface.

Strip away the interface conventions. Find the actual decision, interruption, handoff, or behavior underneath.

CaptureOrganizeRetrieveAct
Clarity over clutter.
03 Build

Make the better interaction tangible.

Turn the reframed problem into something concrete enough to test, refine, and eventually ship.

MaxiMail application, a working product developed in the MMWB Workshop.

Usually, the opportunity shows up before the solution does.

You do not need to know whether the problem is workflow, interface, product logic, data, or the handoffs between them. Most of the time, the first useful signal is simply that something feels harder than it should.

01

The software works.
The workflow doesn’t.

Your team has already built workarounds around the system — extra clicks, duplicate entry, side spreadsheets, manual checks, or messages outside the tool. Nothing is technically broken. Too much effort is required to make it work.

02

The product has grown past its original assumptions.

Features accumulated. Customer behavior changed. What once felt simple now requires explanation, training, memory, or increasingly elaborate navigation.

03

You know what you want to build, but not yet what it should become.

There is a real problem and a real opportunity, but jumping directly into requirements would freeze too many assumptions before the underlying experience is understood.

04

Something feels harder than it should.

You may not yet know whether the issue lives in the workflow, interface, product logic, data, or the seams between them. That uncertainty is often exactly where the useful work begins.

You don’t need the diagnosis before you call us.

Two ways we get involved.
One standard for the result.

Your Software Has a
Better Version of Itself.

Most software improvement starts with a feature list or a replacement search. We start by asking a different question:

What is the current system preventing people from doing naturally?

The answer is often not “buy something new.” It may be a broken handoff, buried capability, bad default, missing piece of context, redundant decision, or an interface that no longer reflects how the work actually happens.

What exists today

Useful assets that are out of alignment.

  • Systems
  • Rules
  • Data
  • Workarounds
  • Employee knowledge
  • Customer behavior
ObserveReframeRedesign
The better version

A system that supports the work again.

  • Less friction
  • Fewer steps
  • Better decisions
  • Useful context
  • Clearer control
  • More value from what you already own
01 — Revenue

Remove friction between intent and action.

Checkout
Lead handling
Conversion decisions
Customer follow-up
Sales handoffs

02 — Clarity

Surface what people are already working to reconstruct.

Existing data
Institutional knowledge
Relationship context
Decision history

03 — Velocity

Collapse unnecessary steps between knowing and doing.

Approvals
Repeated entry
Context switching
Search
Manual coordination

04 — Experience

Make the right way the easier way.

The software should guide good behavior naturally instead of depending on training, memory, and workaround discipline.

No automatic rip-and-replace.
No predetermined stack.
No assumption that technology is the problem.

We find the highest-return improvement in the system you actually have, with the people who actually use it.

More experts. Fewer things that just work.

01Intent over inference. What you explicitly do matters more than what an algorithm guesses you want.
02One step, not five. If a common action takes multiple screens and a detour into settings, it is broken by design.
03Relationship-aware systems. Software should know the shape of the real world it is serving.
Start a conversation

Have something important to build, fix, or launch?

We meet you with the right energy: clear thinking, strong systems, and a human point of view.

Get in touch ↗