Selected work

Bruber

Moving decisions to the moment they matter.

An initial screenshot-upload brief became a native product for understanding ride-offer economics while the decision still matters.

Role
Dimas · Consulting product lead and sole 0-to-1 builder
Scope
Field research · Product direction · Experience design
Stage
Built components; ongoing development

Delivered

Native capture, recognition, economics, background processing, and history components.

Key decision

Move the answer from after the upload to the moment the driver needs to decide.

Evidence

Owner-provided September 2026 case record. Current stage and outcome limits are detailed below.

Read the current stage
  1. Capture the offer

    Visible terms · card-local recognition

  2. Calculate the context

    Explicit economics · vehicle costs

  3. Support the decision

    Native iPhone experience · history

System overview · not an application screenshot

What the client brought

An initial brief for an application that analyzed uploaded ride-offer screenshots.

What the work revealed

Firsthand rideshare work exposed the real constraint: an answer delivered after the driver committed could arrive too late.

The decision that shaped the system

After building the original upload application, Dimas began driving rideshare himself. That experience exposed a timing problem. He proposed shifting the product toward economic context at the offer decision, secured the founders’ agreement, and carried the rework through design and implementation.

What was built

The work connected field research, product direction, experience design, and native iPhone engineering. Dimas built the capture, recognition, calculation, background-processing, and offer-history components, while also supporting organic distribution.

Where judgment mattered

Recognition, calculation, and the driver’s choice have distinct responsibilities. Visible offer terms and configured vehicle costs support explicit projections; AI enrichment can follow later. Technical assumptions were revised when device evidence challenged them.

Current stage

Native components have been implemented and tested, and development continues. The available records do not establish a fully verified public release or an improvement in driver earnings.

Connected responsibilities

  • Field research
  • Product direction
  • Experience design
  • Native engineering
  • Intelligence pipelines
  • Business development

Selected experience of BuildFutures founder Dimas. Adapted from the owner’s September 2026 case records. The diagrams explain system responsibilities; they do not depict a released application or establish commercial outcomes.

Explore all selected work

Bring the problem. We’ll help find the next step.

What needs to work better?

Start a conversation