A working product demonstration

From scattered opportunities
to a plan you can act on.

Change the brief. Compare the evidence. Make the call. Explore how software turns the work between an opportunity and an agreement into one clear experience.

Fictional organizations and sample records. Real filtering, calculations, approval rules, and downloadable outputs. No live AI or external actions.

Cedar & Signal · Fictional product studio

Opportunity StudioInteractive demo

You are choosing a first project for a small software team. The system organizes the opportunity; you decide what the team can commit to.

Runs in this browser
Start with the work you want

Give the system
a useful brief.

A shortlist should reflect your goals and constraints. These choices change the ranking, project economics, and delivery dates.

BRIEF

What the team can deliverFocus, capacity, commercial fit

12 ROWS

Opportunity registerFictional organizations and project needs

EVIDENCE

Briefs & source messagesInspectable facts, with gaps left visible

Dates are illustrative. Team days use weekdays; holidays are not modeled.

Sample pricing assumption$700 per team day. Each project has a full scope and a smaller first release.

Start with a brief. Your choices stay in this page and reset when it reloads.

Brief v1
What makes the workflow work

Useful automation.
Visible judgment.

The interface is only part of the product. The rules between each step keep the work understandable.

01 / Evidence

Keep the basis in view.

Inspect the source record behind a budget or deadline. An unknown stays an unknown; a polished proposal does not make it a fact.

02 / Authority

Approve the actual version.

A change to the scope, timing, or delivery note clears the old approval. Preparation can continue; commitment needs renewed review.

03 / Outcome

Carry the decision forward.

Simulated acceptance produces a dated plan and an export from your choices. Planned tasks stay distinct from completed work.

About this demonstration

The sample register, source messages, and organizations are fictional. Matching uses explicit rules; estimates use a fixed illustrative daily rate. It does not measure actual productivity, predict sales, or establish AI safety. The output is a demonstration artifact.

Read the design principles