Booking new projects

EndekoApp

A method you can plan a budget around

Software projects go over budget when scope, quality and decisions are vague. Our method makes all three explicit, phase by phase, so you always know what you are paying for and what comes next.

§ 01 · Phases

What each phase gives you, and what it needs from you

Phase 1

Discovery

1–2 weeks

You get

  • Scope document with priorities
  • Architecture note
  • Risk list
  • Fixed quote for the next phase

We need from you

Two or three workshops with the people who know the business best.

Phase 2

UX & prototype

2–4 weeks

You get

  • User flows and wireframes
  • Clickable prototype
  • User test findings
  • Visual direction

We need from you

Feedback within two working days on each review round.

Phase 3

Engineering sprints

2-week cycles

You get

  • Working build every sprint
  • Sprint demo and notes
  • Updated backlog and forecast
  • Test reports

We need from you

A product owner who joins sprint reviews and answers questions in chat.

Phase 4

Hardening & launch

1–3 weeks

You get

  • Performance and security review
  • Store submissions
  • Staged rollout
  • Launch day support

We need from you

Final content, legal texts and store account access.

Phase 5

Care & growth

Ongoing

You get

  • Monthly health report
  • Updates and fixes
  • Roadmap delivery
  • Quarterly review

We need from you

A monthly priorities call, about an hour.

§ 02 · Your squad

Small teams, senior people

A typical squad has five to seven people. Everyone has shipped production software for years, and everyone talks to you directly.

Typical share of squad time by role

  • Tech lead18%

    Owns architecture, code quality and technical decisions.

  • Engineers46%

    Two to four, across mobile, web and backend as needed.

  • Product designer14%

    Research, flows, UI and the design system.

  • QA engineer12%

    Test plans, automation and release checks.

  • Delivery manager10%

    Planning, budget tracking and your main point of contact.

§ 03 · Commercial models

Three ways to work together

AspectAFixed-scope phaseBDedicated squadCCare plan
Best forClear goals, defined featuresEvolving products, long roadmapsProducts already in production
PricingFixed price per phaseMonthly fee per squadMonthly fee by plan level
Scope changesChange requests, priced upfrontReprioritised every sprintMonthly backlog review
Typical length1 to 4 months per phase6 months or more12 months, renewed yearly
Notice periodEnd of current phase30 days60 days

§ 04 · Quality gates

Nothing ships without passing these

  1. 1

    Code review

    Every change is reviewed by another engineer before it is merged.

  2. 2

    Automated tests

    Unit, integration and UI tests run on every pull request.

  3. 3

    Accessibility

    Automated checks plus manual screen reader passes on key flows.

  4. 4

    Performance budget

    Load times, bundle sizes and API latency checked against agreed limits.

  5. 5

    Security scan

    Dependency and secret scanning in CI, plus a review before launch.

  6. 6

    Release checklist

    A written checklist signed off for every production release.

Where we collaborate:Linear or JiraFigmaGitHubSlackNotionGoogle Meet

§ 05 · Questions

Before you commit

01How do you estimate projects?

We estimate after discovery, not before. Discovery is a small fixed-price phase that turns ideas into a scope we can price with confidence, and you own its outputs even if you build elsewhere.

02What if our priorities change mid-project?

They usually do, and that is fine. In a dedicated squad we reprioritise every sprint. In a fixed-scope phase we price the change and you decide whether to swap, add or postpone.

03How involved do we need to be?

Expect one person from your side to spend two to four hours a week with us: sprint reviews, quick answers in chat and decisions when they are needed.

04Who owns the intellectual property?

You do. Code, designs and documentation belong to you as soon as they are paid for, and everything lives in your accounts from the start.

05Do you sign NDAs?

Yes, before the first detailed conversation if you like. We can use your template or our mutual one.

06Can you work in our time zone?

We agree a shared working window for each project to keep reviews and communication convenient for both teams.

Have a product in mind?

Send us a short brief, a sketch or a link to what exists today. You will get a reply from an engineer, not a salesperson.

Plan your build[email protected]