Nexoracode

Method

The score, written down

Our method is simple enough to fit on a page and specific enough to hold us to it.

Discovery

Typically one to three weeks

Conversations, existing systems review, task mapping and a first prototype. Ends with a written plan, an estimate range and the assumptions behind it.

Foundations

Usually the first fortnight of build

Repository, pipelines, environments, design tokens and the data model. Unexciting, essential and visible to you.

Phrases

Repeated fortnights

Planning, building, preview, feedback, release. Each phrase has a short written summary.

Launch

Planned from week one

Store submissions, final checks, staged rollout and a watch period during working hours.

Care

Ongoing

Updates, fixes and improvements under an agreed support arrangement.

Standards

  1. Code review on every change. No code reaches the main branch unseen by a second person.
  2. Secrets never in repositories. Keys live in environment configuration with least-privilege access.
  3. Dependencies updated monthly. Security advisories reviewed as they appear.
  4. Accessibility checked every phrase. Keyboard, contrast and screen reader spot checks.
  5. Estimates revisited openly. If scope or assumptions change, you hear about it the same week.
  6. Data minimised. We collect and keep only what the product needs, and document where it lives.
  7. Ownership is yours. Code, designs and documentation belong to you on payment.

How we estimate

Estimates are ranges, not single numbers, and each range comes with the assumptions that would move it. We break work into pieces small enough to reason about, estimate those, add explicit allowances for integration and testing, and show you the arithmetic. When we are uncertain, we say what a short spike would cost to reduce that uncertainty.

Sketch a release rhythm