Knowledgebase

How working with us 
actually works. 

Short, plain guides on starting a project, how it runs, who owns what and how to get help. Written for people who are not engineers.

011 min read

Start with a short brief

You do not need a full specification to begin. A few honest sentences are enough for a useful first answer.

Write a few sentences on each of these points. Rough is fine; we will ask about anything that is unclear.

  • What you want to achieve, and why now
  • Who will use it
  • Any existing systems, code or technology we must work with
  • Deadlines or events that shape the timeline
  • A budget range, if you have one

Send it from the contact page and choose “Start a new project”. If you are not sure which service you need, choose “Not sure yet” and we will help you decide.

A rough budget and timeline are optional, but they make our first reply more useful.

We read every message and reply to the email address you give, either with questions or with a suggested time for an introductory call.

021 min read

How a project runs, stage by stage

Whichever service you start with, the work follows the same five stages, so you always know where you are.

  1. Discover

    We align on goals, constraints and what success looks like before any work is scoped.

  2. Design

    Architecture, user experience and the delivery plan are shaped together, with prototypes you can click before we build.

  3. Build

    Work runs in two-week sprints with a demo at the end of each, plus code review and testing along the way.

  4. Launch

    A planned production rollout, with a launch checklist so nothing is left to chance.

  5. Scale

    Optimisation and long-term support as your product and traffic grow, with Basic, Pro and Enterprise support tiers.

New projects can typically kick off within one to two weeks of signing the agreement. What each support tier includes depends on your project, so ask us when you discuss the engagement.

031 min read

Choosing an engagement model

There are three ways to work with us. The right one depends on how clear the scope is and how much will change.

Fixed price
A defined scope for a set price. Suited to projects with clear requirements and a clear finish line.
Time and materials
You pay for the work as it happens. Suited to products where priorities will change as you learn.
Dedicated team
A team that works as an extension of yours over the long term. Suited to continuing product development.

We choose the model to suit the scope and the risk of the project. Tell us about what you are building and we will recommend one.

041 min read

Picking the right service

Start with the outcome you want rather than the technology. Most projects combine several services.

For example, a new product often pairs product engineering with UI/UX design and API development. This table suggests where to begin for common goals. It is a guide, not a rule.

051 min read

Reporting a problem so it gets fixed fast

A good report saves a round of questions. Here is how to send one and what to put in it.

  1. Open the form

    Use the contact form and choose “Support for an existing project”.

  2. Describe it

    Use the checklist below. The more detail you give, the faster we can find the cause.

  3. Say if it is urgent

    Put that in the first line of your message.

  4. Use an inbox you check

    That is the address we reply to.

Where you can, include:

  • The name of the product or project, and whether the problem is in production or a test environment
  • What you expected to happen and what happened instead
  • When it started and how often it happens
  • The steps to reproduce it, if you know them
  • Error messages, logs or screenshots
  • How much it affects your users or your business

061 min read

Ownership, NDAs and your data

Who owns what, what we keep confidential, and what happens to the details you send us.

NDAs
We sign mutual NDAs before work starts, and every teammate signs an NDA before onboarding.
Code and IP
After the project is complete and paid for, you own 100% of the IP.
Security practice
We follow OWASP best practices and use encryption. GDPR, HIPAA and PCI-DSS needs can be supported and are scoped with you at the start of the project.
This website
Messages sent through the contact form are emailed to our team so we can reply to you, and we use your details only for that.

Reference

Words you will hear

Plain definitions, so no meeting starts with a vocabulary test.

Discovery
The first stage, where goals, constraints and success measures are agreed before anything is built.
MVP
Minimum viable product: the smallest version that real users can use and that teaches you something.
Sprint
A fixed block of work, here two weeks, that ends with something you can see.
Demo
A short walkthrough of working software at the end of a sprint.
Prototype
A clickable mock-up used to test an idea or a flow before it is built.
Handoff
Passing finished work, code and documentation to you or your team.
IP
Intellectual property: the code, designs and documents produced for your project.
Staging
A private copy of the product used to check changes before they go live.

Still growing

More guides are on the way

We are a new team and we add a guide whenever the same question comes up twice. Need a quick answer today? The Help Center has short ones.

Open the Help Center

Planned

  • 01

    Security review guidelines

    What we check before a production launch.

    Planned
  • 02

    Launch checklist

    The steps we walk through on go-live day.

    Planned
  • 03

    Handoff documentation

    What you receive when a project is delivered.

    Planned
ElvixTech

New ideas. Fresh energy. Real dedication. A new team building web, mobile and SaaS products, with your success as our first milestone.

© 2026 ElvixTech. All rights reserved.

Privacy policy