From first call to first release: how a project starts

Most delays happen before a line of code is written: unclear scope, a contract nobody can read, a team assembled in a hurry. Our start takes five steps, and each one ends with something you can hold.

1. Initial call

We talk about the business goal, the users, the deadline and the constraints, and check the fit honestly. If the project is not ours, we say so.

You get: a short summary of what we heard and the questions still open.

2. Q&A and rough estimate

We clarify the open questions in writing, then estimate the scope by features and roles.

You get: a range of time and cost with the assumptions behind it. Free and non-binding.

3. Agreement

Scope, budget, timeline and payment terms go into a clear contract. If you need an NDA, we sign it before you share anything sensitive.

You get: a contract where every deliverable has a date. No upfront payment on outsourced development and staff augmentation.

4. Discovery

A business analyst, designers and a tech lead turn the idea into requirements, user flows, a design direction and an architecture.

You get: a backlog ordered by value, a clickable design and a technical plan you can show to investors.

5. Build and release

Two-week sprints. Each sprint ends with a demo of working software, not slides. QA runs inside the sprint, not after it.

You get: working software every two weeks, the release, and support after launch.

What stays the same the whole way

  • You know who works on your project and talk to them directly.
  • If the first week does not work for you, you do not pay for it.
  • Progress is visible every two weeks, in the product itself.

Planning a product?

Book a call and get a rough estimate of time and cost - free, before any contract.