Nexux Labs

How we work

A process designed so you are never guessing

Five stages, each ending in something you can see. A written scope, written changes, and everything in your own accounts from day one.

Commitments

Six things we promise, and you can hold us to

Not values on a wall. These are specific, checkable commitments, and you should ask us about any of them on the first call.

A preview link in week one

You see real progress on a real URL from the start. No month-long silence followed by a reveal.

You talk to the builders

No account manager in the middle. The people answering your questions are the people writing the code.

Written scope, written changes

What is included is in writing. Anything that changes cost or timeline is a short note you approve first.

Everything in your name

Repository, domain, hosting and third-party accounts are yours from day one.

We will talk you out of things

If a feature is not worth building, or continuing beats rebuilding even though we earn less, we say so.

Handover that actually works

Documentation and a recorded walkthrough, written for a developer who has never met us.

The process

Five stages, and exactly what each one produces

Including what we need from you, because the honest bottleneck on most projects is feedback and content, not development.

01

Discovery

3-5 days

Before anything is designed we establish what success looks like in a measurable way, and what constraints are real. A surprising number of projects are rescued at this stage by removing something nobody actually needed.

What happens

  • A working session on goals, users and constraints
  • Review of your current site, app or process
  • Agreement on the one measure that defines success
  • Technical review of hosting, integrations and data

What you receive

  • Written scope with phases
  • Sitemap or screen list
  • Timeline with milestones
  • Fixed quote

What we need from you

Two to three hours of someone who can make decisions, plus access to what exists today.

02

Design

1-3 weeks

We settle structure before visuals, because moving a step in a flow costs nothing in a wireframe and a great deal in a built screen. You approve direction on the key screens before the rest are produced.

What happens

  • Flows and wireframes for the core journeys
  • Visual design of the primary templates
  • Component and token definition
  • Accessibility check on contrast, focus and targets

What you receive

  • Clickable prototype
  • Design system in Figma
  • Content requirements per page
  • Approved key screens

What we need from you

One named approver, feedback in the prototype, and your content or a decision to have us write it.

03

Build

2-10 weeks

Development in reviewable slices against a live preview link. You see pages and features appear one at a time, so feedback arrives while it is still cheap to act on.

What happens

  • Front-end build from the approved design system
  • APIs, database and integrations
  • Weekly preview builds and a written progress note
  • Tests on the journeys that matter

What you receive

  • Preview environment you can visit any time
  • Working features behind a weekly changelog
  • Admin or CMS access as soon as it exists
  • Source code in your repository

What we need from you

A weekly look at the preview and quick answers on anything blocking.

04

Launch

2-5 days

The deliberately dull phase. Performance, SEO, analytics, redirects, backups and monitoring are all done before DNS changes, and we have a written rollback if anything goes wrong.

What happens

  • Performance and Core Web Vitals pass
  • Metadata, sitemap, robots and structured data
  • Redirects from old URLs, analytics and Search Console
  • Backups, monitoring and SSL verification

What you receive

  • Live site or app on your infrastructure
  • Launch checklist, signed off
  • Handover walkthrough and recording
  • Documentation for content and admin

What we need from you

Domain and hosting access, and someone available on launch day.

05

Support

Ongoing

Thirty days of bug fixing is included with every project. After that you can take it in house with the documentation we provide, or keep us on a maintenance retainer.

What happens

  • Bug fixes on what we built, free for thirty days
  • Monitoring of real traffic and errors
  • Dependency and server patching on a retainer
  • A review of what the numbers say after launch

What you receive

  • Fixes shipped during the warranty window
  • Monthly maintenance report, if retained
  • Backup and restore verification
  • A prioritised list of what to do next

What we need from you

Tell us what breaks, and decide whether to retain us or run it yourselves.

Engagement models

Four ways to work with us

We recommend the one that fits your situation, not the one that bills the most. Pricing is quoted per project after a discovery call.

Fixed-scope project

Deposit, then payment per milestone

A defined deliverable with a written scope, a timeline and milestone payments. The right model when you know what you need built.

Best for

Websites, mobile apps and first versions of a product

  • Written scope with phases and deliverables
  • Fixed price agreed before work starts
  • Milestone payments tied to delivery
  • Change notes for anything outside scope
  • Thirty days of post-launch bug fixing
Ask about this model

Dedicated team

Monthly retainer

A monthly block of our capacity working to your priorities, re-planned every two weeks. The right model when the roadmap is still moving.

Best for

Products in active development with changing priorities

  • Named engineers and designers on your project
  • Two-week planning cycles you take part in
  • Direct access to the people building it
  • Monthly summary of what shipped
  • Scale up or down with one month of notice
Ask about this model

Maintenance & support

Monthly retainer

Someone responsible for keeping what you already have patched, backed up, monitored and working.

Best for

Live sites and apps the business depends on

  • Dependency and server patching
  • Backup verification and restore drills
  • Uptime, error and certificate monitoring
  • Small content and layout changes
  • Agreed response time, in writing
Ask about this model

Audit & consulting

Fixed fee per audit

A short, bounded piece of work that produces a decision: a code review, a performance audit, a security review or an architecture opinion.

Best for

Teams deciding whether to fix, rebuild or change direction

  • Review of code, infrastructure or UX as scoped
  • Prioritised written findings with reproduction steps
  • Costed options rather than a single recommendation
  • A call to walk through the report
  • No obligation to have us do the work
Ask about this model

Cost and timelines

The money questions, answered plainly

Including why we do not publish a price list.

Every other question

It depends on scope, and anyone who quotes before understanding the scope is guessing. What we can promise is a written, itemised quote after one discovery call, so you can see what each part costs and remove anything you do not need.

Ready to scope something properly?

One call, no obligation, and you leave with a clear view of scope, timeline and cost.

whatsapp-icon Nexux