runpoint.

Decisions by Runpoint

Your leaders review each plan and give an answer within two days.

With Runpoint Decisions, your office manager, dispatcher and a lead technician click through each new screen and tell us what to change before we build it.

We use it on every Runpoint project.

Watch a review from start to finish
A project manager in a safety vest and a client's facilities director review a laptop together in a site trailer, with steel framing and new rooftop units outside.
02Waiting on answers

Software projects slow down while people wait for feedback and approvals.

A question sent to a group chat of twelve people can sit for days, because everyone assumes someone else will answer it.

Seven rounds of documents and meetings become one review of a working screen
Seven rounds of documents and meetings become one review of a working screen
WaySteps
The usual wayUser stories, Persona maps, A 15-page spec, Data spreadsheet, Design review, Architecture review, Prototype rounds
How we work, with DecisionsA working screen, Everyone comments, An answer in two days
Matthew Hall and Ryan Mish in the Decisions film.
03How a review works

Everyone who has to approve the work sees it, comments on it and answers.

Here is one review: the first full pass at a shift planner for a sample manufacturer, with five approvers and two days on the clock.

  1. 01

    We send a working screen

    Your people click through a working version of the new screen instead of reading a long document.

  2. 02

    We ask the questions that matter

    A short note says what the screen is for and the few questions we need answered before we build.

  3. 03

    People comment on the exact spot

    Anyone can drop a pin where they mean, and the right person replies in the same thread.

  4. 04

    Each approver gives an answer

    Approve, ask for changes, or decline and set up time to talk, and everyone sees who has answered.

Runpoint Decisions with Northstar, a sample manufacturer. Fictional data.

04Where it fits

Decisions comes after we find the problem and before we build the fix.

Every system we build for a contractor goes through the same four steps.

  1. 01 · Papercuts

    Find what to fix

    About two weeks

    We listen to your people and rank what slows them down.

    Papercuts

  2. 02 · Decisions

    Approve the plan

    Answers within two days

    Your leaders click through working screens and tell us what to change.

  3. 03 · Foundation

    Build the system

    Two to three months

    We build your system on software we have already built and tested.

    Foundation

  4. 04 · After launch

    Keep it running

    Ongoing

    We look after it, or we train someone on your team to do it.

    After launch

05Watch

Watch one of our engineers take a new screen through a review.

Matthew Hall and Ryan Mish, the engineer who built Decisions, review a new sales screen for Halden Build Group, a sample construction company.

Runpoint Decisions · 9:27Read the transcript
06Contact

Want to see how your team would review a build?

Tell us what you're planning to build, and after about two weeks of discovery your leaders will review the first plan in Decisions.

Start with two weeks of discovery