How a project runs

First call

We ask what you want to build, who will use it and what happens if it is not built. We also tell you plainly if we think there is a cheaper way.
From you: a rough description and any examples you like
Written scope and quote

You get a document listing what will be built, what will not, how long it should take and what it costs. Work starts only after you agree to it.
From you: a yes, a no, or changes to the scope
Design

For anything with screens, we design first. You review wireframes and a prototype and change things before any code exists.
From you: feedback on each round, ideally from the people who will use it
Build in short cycles

We build in blocks of about two weeks. At the end of each, you get a working version you can click through on a test address.
From you: a quick review after each cycle
Testing and launch

We test on real devices and browsers, then deploy to your server or hosting account. We keep the release steps written down so they can be repeated.
From you: access to hosting, domain and any third-party accounts
After launch

We fix problems that come from our work. After that you can maintain it yourself, hire us on a monthly support plan, or hand the code to another developer.
From you: tell us what real users run into

You do. Once the project is paid for, the code and design files are yours, and we hand them over with notes on how to run them.

Defined projects get a fixed quote based on the written scope. Open-ended work is billed monthly. We do not give prices before we understand the job.

Ready to start with step one?