App development For a product that doesn't exist yet

We build the app. You see every step.

You describe what the business needs. We turn it into a working product, with every screen agreed before any coding, progress you can see at any time, and a written report every two weeks.

For
A company that needs an app built and has no team to build it, or a team with no room for it
How it runs
The brief, the wireframes, the build, the report
Who builds it
Our developers, under our CTO's technical direction
First step
A call about what you want built

Who it's for

You know what the business needs and you want it built properly, by people who will show you the work as it happens. You don't want to hire a team to get there, and you don't want to judge the technical decisions yourself.

Our CTO turns what the business needs into technical decisions, so the part you were never meant to judge stops being your problem.

How we build it In the order it happens

Every step is something you can see.

  1. 1 · The brief

    You describe what the business needs, in plain language.

    We write it up as a short brief: the problem, the goals, what you will provide, what you will get, and how we will know it is right. You confirm it before anything else happens.

    You see: the brief, in your words.

  2. 2 · The wireframes

    Every screen is drawn and agreed before any coding.

    We draw every screen of the product and walk you through it as a workflow, step by step: what the user does, what the system does, and what happens when something goes wrong. You agree to that set, and it becomes the scope of the work.

    You see: the full set of screens, walked through with you.

    A wireframe workflow board: four gray screens in order, each with what the user does, what the system does, and the states it can be in.
    One workflow from a product we are building now, as the client reviewed it. Drag sideways to follow it, or click to open it full size.

  3. 3 · The build

    Drawings become working pages, step by step.

    Each approved screen moves from drawing to working page, so you can see progress at any time. Every change passes the same checks before it ships.

    You see: each screen as it moves from drawing to finished.

    The page, as we build it

    The report, as it ships

    LiveShift's operations report: the page as we build it, and the report a customer receives (sample data).

  4. 4 · The report

    Every two weeks, a written report and a session to walk through it.

    You hear what was finished, what is next, and what we need from you, in plain language. You never have to read code.

    You see: the report, and the product as it stands.

Who does the work

Our own developers, working the way a Viable Teams developer does: on our Viable Coding setup, under our CTO's technical direction, with project management included. If you'd rather have the developer sit on your own team, that is Viable Teams.

What stays with you

The product, its wireframes, the code, and the setup it was built on. Everything we put in stays with you.

We built our own products this way: LiveShift from start to finish, and a new product right now, from its wireframes up.