Start a project
Contact

Tell us what you run.

A paragraph is enough to start. We read every brief ourselves and get back to you as soon as we can with a considered view, not a calendar link.

What happens next

  1. Day 0

    You send a brief

    The problem, who lives with it, and any constraint you already know about. Rough is fine.

  2. Shortly after

    We reply with a view

    What we think you should build, what we would cut, and whether we are the right team for it.

  3. Week 1

    A 30-minute call

    No deck. We ask about the environment, the systems already in place, and what happens if nothing changes.

  4. Week 2

    Scoped proposal

    Fixed discovery scope, timeline and price, with a written output you keep regardless of what follows.

Email us directlyhello@aurezalabs.com
Response timeAs soon as we can, on every brief
Where we workRemote, worldwide, with overlapping hours agreed up front
ConfidentialityNDA on request, signed before anything is shared
Accepting projects

Project brief

The fields marked required are the only ones we actually need.

What do you need?

No retainers required · NDA on request · We reply to every brief

Brief received.

Thank you. We read every brief ourselves, and you will hear back from us as soon as possible.

Working with us

The operational problem in plain language, who lives with it day to day, what systems are already in place, and what happens if nothing changes. You do not need a specification; if you had one, you would need us less.
Yes, on request and before anything substantive is shared. Send the brief at whatever level of detail you are comfortable with, ask for an NDA in it, and we will have one back to you the same day.
Sometimes. If the work is genuinely small we will often say so and point you at a simpler answer, including one that does not involve hiring us. Discovery is the honest starting point for anything either side is unsure about.
Yes. We run as an embedded team alongside client engineers on roughly half our projects. Where your team will own the result afterwards, handover and training go into the schedule rather than getting bolted on at the end.
That is a common first conversation. We will review what exists and tell you honestly whether it is worth continuing, refactoring or replacing, including when the answer is that your existing team should finish it.