Facing a challenge with your product? Let's have a call, a coffee, whatever works for you.
Why MacetaServicesHow We WorkTeamCasesCompany Brain

Work Proposal

A Diagnosis doesn't end in a fixed package.

It ends in a plan built around what we actually find in your product: sometimes that's one thing to fix, sometimes several at once. That's how we think about every Work Proposal.

01

What a Diagnosis actually evaluates

We don't start from a service to sell you. We start from three questions: does your product have a validated foundation? Does the experience it offers convert and retain? Does your team hold, week after week, the product judgment it needs to stop making the same call twice? The three answers rarely land on the same side. Your Work Proposal gets built around what we find in each one, not a fixed menu.

We always take time to diagnose before proposing anything, and how much depends on the case: sometimes a 25-minute call is enough, sometimes it's up to 10 business days of our own work. It never costs anything and is never billed separately. When it's the full pass, it ends in two documents: an analysis of where things stand with recommendations, and the Work Proposal itself.

02

When the direction is missing: Product Strategy

Most teams aren't short on ideas. They're short on data confirming that the idea in front of them is worth building for the next six months. So they ship it anyway, adoption never takes off, and the debate becomes whether the problem was the feature or the execution. A debate nobody wins, because nobody wrote down what "working" was supposed to mean.

When we find this, we validate that foundation: we turn what your team already senses about the market into a roadmap tested with real users, not assumed in a meeting room, and into a North Star Metric with the input metrics that actually move it.

What it moves: time to a validated roadmap, and the share of your dev budget that goes toward what users actually adopt.

03

When the direction holds but nobody's tested if the experience converts: Product Design

A product can have a clear strategy and still lose users along the way, because strategy defines what to build, not whether the way it got built works for the people using it. The problem is rarely on the screen you're looking at: it's friction nobody measured, a flow designed once and never tested against real users again.

When we find this, we redesign those flows with data and judgment: conversations with real users, friction points identified and prioritized, and every decision about what converts and why, written down, not just shipped.

What it moves: conversion and retention, measured before and after, not an interface that just looks tidier.

04

Why they're two services and not one

For a while we sold them together, and there was a good reason: separating direction from design lets someone buy screens without knowing what they're for. That reason still holds, so we didn't drop it. We turned it into an entry condition: Product Design doesn't start without a defined problem and user, and if the Diagnosis finds the decisions were made on opinion, we start with Strategy.

What you get from them being two is that you buy only what you need. Plenty of cases already have the direction and what's missing is making it usable. Others are the reverse. Sold as one project, each case also paid for the half it didn't need.

05

When the product is fine but the judgment doesn't hold: Product Mentorship

Some teams' problem is neither strategy nor design: it's that nobody's thinking about the product with the same seriousness week after week, and that judgment never gets written down anywhere, so it disappears the moment that person leaves or the team outgrows fitting in one head.

When we find this, the work becomes ongoing: recurring strategy and roadmap sessions at a cadence we set together, and a decision log with an owner and a review date that your team actually checks before the next call instead of re-litigating it. We're the judgment, not the hands: a steady place to think before investing, without adding a full-time CPO.

What it moves: how long it takes the team to decide, and how much of what gets decided today ends up reversed six months from now.

06

When what's needed isn't work but a read: Product Audit

Sometimes the diagnosis concludes there's no work to propose yet: that the question isn't what to build or how to decide better, but how solid this is before putting more capital or more time behind it.

The Audit is a closed, independent evaluation. We look at what data exists that the problem matters and which critical assumptions were never validated, what product decisions were made and on what data, where the adoption friction is, and who decides product today and who it depends on too heavily. You end with an executive memo carrying prioritized risks, real strengths and warning signals, plus a validation plan: what to validate first, what to pause, which risk needs an owner.

We build nothing. It isn't financial, legal or technical due diligence, and it doesn't certify that an investment will work. And "don't do anything yet" is a complete outcome, not a failed audit.

07

Most of the time, it's a combination

If the foundation isn't validated, there's no reliable way to know who the experience is even being designed for: redesigning flows without that foundation is betting twice instead of once. So when the foundation is missing, the work usually starts there and only then moves into experience. Different case: a team that already validated its foundation and tested its experience, but has nobody holding that judgment over time; there, the project closes and the accompaniment continues. The Diagnosis exists to see which of these is your case before we propose anything.

08

Why you won't find a price list

Price and duration for every service come out of the Diagnosis, always, and that's deliberate. A service with a published price is a package, and a package makes you pay for what you don't need in order to get what you do. We'd rather build each proposal on what we found: scope comes from the Diagnosis, and the number comes from the scope.

Let's talk for 25 minutes and go through it together. That's where your Diagnosis comes from, and from there, your Work Proposal.

Let's talk

Thanks, your message was sent. We'll get back to you soon.

Tell us about your project