Choose the right priority.
The roadmap is full, but the next product decision is unclear.
Agreed output
A shared problem definition and prioritized workflow.
Strategy + design for water-software teams
For founders and product leaders serving utilities and operators. Clarify the priority, prototype the workflow and give your team a clear plan to build from.
Design: $5,000/month.
Scope and availability discussed before we start.
Selected water-software work
A real product-design example from the public portfolio: an IoT monitoring interface with integrated alarm management.
From data to decisions
When more features aren’t the answer
Monitoring, alarms, asset information and operational handoffs carry a lot of context. Start with the decision that matters most and agree on the outputs around it.
The roadmap is full, but the next product decision is unclear.
Agreed output
A shared problem definition and prioritized workflow.
Operators have to reconstruct context across screens and handoffs.
Agreed output
A workflow map and a prototype of the agreed priority flow.
New screens and patterns keep pulling the product in different directions.
Agreed output
Documented decisions, component patterns and implementation considerations.
The working model
Senior strategy and product design, in a recurring engagement. We confirm fit, priorities and availability on the intro call before defining the work.
Design subscription
A fit for water-software founders and product leaders with a priority workflow to improve and a team to collaborate on the decisions.
Book a 30-minute introCompare subscriptions and fixed-scope projectsDesign + Build is $9,000/month. Fixed-scope projects start at $20,000, with a final quote based on scope.
No obligation. We’ll discuss the challenge and whether an engagement makes sense.
The agreed scope can include
Direct collaboration with a senior practitioner. Scope depends on product complexity, access to users and your team’s availability.
A realistic first month
We agree on the scope around your product complexity, access to users and team availability.
Review your product and current evidence. Agree on the people, workflow and decision that matter most.
Make the handoffs visible and compare the options worth pursuing.
Prototype the priority flow. Review with your team and users when access is available.
Document the decisions and implementation considerations. Agree on the next month’s priorities.
This is a collaboration plan, not a promise to redesign your entire platform in four weeks.
Before you book
We spend 30 minutes discussing your product, the workflow or decision that needs attention, and whether the engagement fits. We discuss scope, timing and availability before any work starts. There’s no obligation to proceed.
Your current product or prototype, the evidence you already have, and the people involved in the priority decision. Reviews with operators or customers depend on access. We agree on team involvement when defining the scope.
The first month focuses on an agreed priority workflow. Its scope depends on product complexity, user access and your team’s availability. It is not a promise to redesign the entire platform in four weeks.
The engagement focuses on product strategy and design, with documented decisions, component patterns and implementation considerations for the handoff. We agree on the scope and implementation responsibilities before starting.
Your next product decision
Tell us about your product and the decision ahead. We’ll discuss fit, timing and a realistic scope for strategy and design.
30 minutes. No obligation to proceed.
Share who uses your product, the workflow that needs attention and the decision you need to make.