Skip to content

Business05

Support business

WEB & APPDEVELOPMENTWeb & App Development

From planning through design and engineering to running it after launch. Web and app development, built as one continuous piece of work.

A wireframe drawn by hand in ink on paper: screen frames, crossed boxes marking where pictures go, and ruled lines standing in for body copy.
  1. Plan

    Decide what to make

    Start here

  2. Design

    Draw the screens

  3. Build

    Ship it

  4. Run

    Keep it running

01Scope

Web, apps, and what happens after

You can come to us before it is decided what to build. From working out what should exist through to changing it after launch, one team holds all of it.

Web

Sites and campaigns

Corporate, brand, campaign. Designed around who updates it after launch, not only around how it looks.

App / Tool

Apps and internal tools

From things fans use to things the company uses. Built on the assumption they get opened every day.

Platform

Platforms and plumbing

Membership, data, delivery. Built so that features can be added later.

Screen layouts open on a monitor, several arrangements side by side.
02Process

Four stages, and no big bang

We do not decide everything up front. Each stage decides only what the next one needs, and what comes out at the end of each is agreed before we start.

  1. Plan

    Deciding what to make

    The goal, the audience, and what we are not doing. Drawing screens before that is settled is how a project gets built twice.

    What comes outRequirement notes / how it will run

  2. Design

    Drawing it

    Screens and flows, close enough to the real thing to be judged — including where the words and the pictures go.

    What comes outScreen design / visual design

  3. Build

    Building it

    Loading speed, how it behaves on a phone, and how it looks when someone shares it are part of the build rather than extras.

    What comes outA service ready to launch

  4. Run

    Running it

    Launch is the short part. Updates, measurement and changes stay with the people who built it.

    What comes outAn arrangement for updates

In-house

We build our own first

This is not a division that only takes contract work. We build the services and the sites we use ourselves, and we run them ourselves. That is why we can design with what happens after launch already in view.

The site you are reading was built in-house too.

03How To Start

You do not need it specified

Before an estimate, a conversation about what should be built is enough. The less fixed the requirements are, the more we can put on the table.

Fine to leave open

  • The shape of the budget
  • A list of screens or features
  • The technology

Helpful to have

  • Why you want it
  • Who it is for
  • Roughly when

In the first conversation we work out the approach and the rough size together. The estimate comes after that.

Start withthe idea.

Enquiries before the requirements are fixed are welcome. The form opens in a new tab and is in Japanese. We reply within two business days, and the person who reads it runs the business.