Skip to content
Ordolith

Process & pricing

How a project runs, and what it costs.

Every project starts with a free intro call and a short paid discovery, and ends with software you own. Here is each step, what you get, and when payment is due.

How a project runs

You approve each phase before the next one starts.

  1. Plan

    1. 01

      Discover

      We map how the work moves today and where it breaks.

      You get: A written map of how the work moves today and what to change.

      Payment: A free intro call first. Then $250, credited in full to the build if you go ahead.

    2. 02

      Propose

      You get: A fixed scope, timeline and price, in writing. Nothing is built until you approve it.

    3. 03

      Prototype

      Clickable screens you can try before anything is built.

      You get: Clickable screens to try and change before the build.

      Payment: 20% to start the prototype.

  2. Build

    1. 04

      Build

      You get: Working software in short rounds, shown as it grows.

      Payment: 60% across the build milestones, in equal parts.

    2. 05

      Test

      Checked against the agreed scope, with your real cases.

      You get: An agreed demonstration against the scope, with your real cases.

  3. Run

    1. 06

      Launch

      Deployed and handed over, with a walkthrough for your team.

      You get: The system live, a walkthrough for your team, and the source code and documentation.

      Payment: 20% at acceptance and handover.

    2. 07

      Support

      Fixes, changes and improvements after launch, if you want them.

      You get: Fixes, changes and improvements on a monthly retainer, if you want one.

Starting prices

Every project gets a fixed price in its written proposal. These are where projects start.

Prices are in USD. Timelines start after discovery and depend on how quickly feedback comes back.

When you pay

  1. 20%

    to start the prototype

  2. 60%

    across the build milestones, in equal parts

  3. 20%

    at acceptance and handover

Your proposal sets the milestones: usually two to four, or one or two for a focused tool.

What moves the price

  • How many processes and screens.
  • How many user roles, and what each can do.
  • The systems we connect to.
  • How much existing data needs moving and cleaning.
  • Hosting and third-party subscriptions, which are quoted separately.

What every proposal sets out

  • Deliverables and how they’re accepted.
  • User roles, screens and workflows.
  • Integrations and their limits.
  • Who moves and cleans the data.
  • Hosting and subscription costs.
  • Rounds of revisions.
  • Your part, and approval times.
  • Payment milestones.
  • How changes are requested and priced.
  • Source code and ownership.
  • Warranty and support.

Start with one conversation

Tell us what you need built, connected or looked after, and we'll reply with how we'd approach it.

  • Fixed scope, agreed up front

    You approve what's built and what it costs before work starts.

  • You own what we build

    Source code and documentation are handed over at launch.

  • Working across time zones

    We work with clients worldwide and keep regular overlap with your business hours.

  • Support after launch

    Optional ongoing support, agreed separately.