Services

Decide it, build it, keep it running.

We design and build digital products — web apps and dashboards, mobile apps, and the integrations that connect them. Three engagements cover the work, each one paid and each one with a defined end. Most teams start with the first.We design and build digital products — web apps and dashboards, mobile apps, and the integrations that connect them. Three engagements cover the work, each one paid and each one with a defined end.

Product BlueprintLaunch SprintProduct Care

Product Blueprint · Launch Sprint · Product Care

See what we have built

What we build

Three kinds of product.

Most engagements are one of these. Several are two of them talking to each other.

  • Web apps & dashboards

    Internal tools, operations platforms and customer-facing apps — the screens a team lives in all day. Roles and permissions, reporting that reconciles, and states that hold up when two people act at once.

  • Mobile apps

    iOS and Android for work that happens away from a desk — drivers, field staff, customers at a counter. Built to stay useful on a bad connection and to reconcile cleanly when it comes back.

  • Integrations & automation

    The wiring between systems that were never meant to talk — payment rails, loyalty engines, ERPs, queues. One contract in the middle, so a change on one side does not quietly break the other.

How we work

Three engagements.

Each one is paid, each one has a defined end, and each one is useful on its own. They compose in order, but none of them obliges you to the next.

  • Product Blueprint

    For
    For a high-stakes workflow that needs clarity before anyone writes code.
    You get
    A decision-ready direction: the scope, the technical plan, the risks named out loud, and an estimate you can hold us to.
    It stops at
    A foundation, not a disguised build. No production code ships in a Blueprint.

    Then→ Most continue into a Launch Sprint. Yours does not have to; the plan is yours either way.

  • Launch Sprint

    For
    For a defined product or workflow that is ready to become a working release.
    You get
    A usable product in production, the essentials connected, and the decisions behind it written down rather than carried in someone's head.
    It stops at
    The agreed outcome, not an open-ended feature list. New scope is a new agreement, said plainly.

    Then→ Hand it to your own team with the handover done properly, or continue into Product Care.

  • Product Care

    For
    For a live product that needs deliberate improvement — not a help desk.
    You get
    Agreed capacity each month for prioritised fixes, refinements and the next increment, against a backlog you own.
    It stops at
    The priorities you set. It is not an open retainer, and it is not on-call cover.

    Then→ It runs for as long as it earns its place, and ends cleanly when it stops earning it.

The path

They compose, in that order.

You can start anywhere. Most teams start at the left, because the cheapest place to change your mind is before the build.

  1. Product Blueprint

    Work out what is worth building.

  2. Launch Sprint

    Build it and put it in production.

  3. Product Care

    Keep it working and keep it moving.

Who does the work

A small team, named up front.

Kepler Dev is a founder-led studio. Mahmoud Attia is accountable for technical direction and delivery on every engagement, and specialists join for the parts that genuinely need them — design, mobile, infrastructure. You are told who is working on your product and what they are doing before they start, not after. We would rather turn work down than staff it with people we cannot vouch for.

Pricing

Priced per engagement, once we understand the work.

There is no rate card, because the honest price depends on scope, risk and how much ownership you want us to carry. We would rather give you a number we can stand behind than one that quietly changes in week three.

How it is set
A project review first, then a written scope with a price against it.
What you own
Ownership and handover are agreed in writing before the work starts.

Tell us what you are trying to build.

A project review is a working conversation about the problem, not a pitch. You leave it knowing whether we are the right studio for it.

Request a project review