Four phases. No theatre.

Common questions about the process.

What clients ask before they say yes.

• How long does the discovery phase typically take?+

  Between three days and two weeks, depending on complexity and how many stakeholders need to be involved. For a focused marketing site, two meetings often suffice. For a multi-tenant SaaS with three user groups + compliance requirements, 8–12 hours of interview time spread over two weeks is more realistic. Important: discovery isn't a "free pitch". It's billed as the first real block of work, if you don't want to continue building afterwards, you still have a cleanly documented discovery to take with you.

• What if the scope changes after phase 2?+

  That's exactly what the phases are cut for. The architecture phase is the last realistic place where you can change scope without pain, after that there's code that needs to be adapted. But everything is deliberately built so pivots are also possible within the build phase: slice planning is reassessed every two weeks, feature flags allow rolling away without rollback stress, and the repo documents why each choice was made, so a later change doesn't mean: "why was it actually done this way?".

• Do you do sprint planning, stand-ups, retros, the whole Scrum apparatus?+

  Every two weeks a slice ships with a short status update. If needed, a 30-minute meeting, otherwise coordination runs asynchronously. Retros after each slice in writing, not as a 90-min workshop. Half the Scrum rituals are bureaucracy that small teams don't need. The other half, slice demo, written update, clear next step, is useful. Those stay.

• Can we work along if we have our own developers?+

  Yes, and it usually makes the result better, because you bring domain knowledge that could never be caught up from the outside. Three models are on the table, depending on team bandwidth: (1) method64 builds, your team reviews PRs and takes over after 4–8 weeks, lift-out scenario. (2) Mixed pair: method64 and your senior work on the same slice, you learn the stack while it's being built, competence transfer. (3) method64 builds frontend, you build backend (or vice versa), when you're strong in one and outsource the other. Which model fits gets clarified in discovery, usually it follows from your team's capacity.

• What happens after the 4 weeks of hypercare?+

  Three options. (a) Pay-per-use: you reach out when something's up; billing is by the hour. No minimum retainer. (b) Fixed hour budget per month (typically 4–16 hrs), included maintenance + monitoring reviews + small adjustments. (c) Lift-out: handover sessions for your team, after that the product runs entirely with you. The usual recommendation is (a) first, when volume becomes noticeable, switch to (b).