Skip to content
Quantum Code.
Quantum Code.
Send an enquiry
info@quantumcode.hr
HREN
Local time in Split: Split,

Process

What working together looks like

From the first conversation to maintenance. No jargon, and a clear list of what you receive at each step.

01 / Five steps

  1. Step 01 / 05

    Discovery

    A conversation of about thirty minutes, in person in Split or on a call. You describe the problem, we ask questions. If we are not the right fit for the job, we say so straight away.

    You receive

    • A written summary of the conversation
    • A list of open questions
    • A rough price and timeline range

  2. Step 02 / 05

    Proposal and quote

    You receive a document with scope, phases, deadlines and a fixed price per phase. Everything out of scope is listed clearly, so there are no surprises later.

    You receive

    • Scope of work by phase
    • A fixed price and payment schedule
    • A list of what we need from you

  3. Step 03 / 05

    Design and build

    We work in short cycles. Every week you see the real state on a staging address, not a slide deck. Infrastructure work happens in agreed maintenance windows.

    You receive

    • A staging address or test environment
    • A weekly written progress update
    • The chance to change course before it gets expensive

  4. Step 04 / 05

    Launch

    Launch follows a checklist: speed, accessibility, security headers, backups, redirects. There is also a rollback plan in case something is not right.

    You receive

    • The system in production
    • Credentials and the source code
    • Documentation and a short training session

  5. Step 05 / 05

    Support and growth

    We do not disappear after launch. Maintenance, monitoring and a monthly report are agreed as needed, with no contract that locks you in for years.

    You receive

    • Regular updates and security patches
    • A monthly status review
    • A direct number and address for emergencies

02 / Details

01

What we need from you

Projects rarely run late because of code. They run late because of content and decisions. So we settle that at the start.

  • One person who makes decisions and replies within two working days
  • Access to existing systems: domain, hosting, social accounts, network equipment
  • Content only you have: photos, price lists, company details
  • For infrastructure: the windows in which work on the system is allowed

02

Communication rhythm

Often enough that you know where we are, rarely enough that you can get on with your own work.

  • A weekly written update: done, next, what is waiting on you
  • A short call when needed, not on a schedule
  • Email for anything that should stay on record
  • Production emergencies: phone, immediately

03

Tools

We use the tools you already have whenever possible. We do not introduce a new system just because we prefer it.

  • Code: a Git repository you own
  • Staging: Vercel preview addresses for every change
  • Documentation: SharePoint or the shared folder you already use
  • Reporting: Power BI, Search Console, Meta Business Suite

04

Handover

At the end of the project the system is yours, together with everything someone else would need to take it over.

  • Source code and change history
  • All accounts and licences in your name
  • Documentation: how it works, how to maintain it, what to do when it stops
  • Training for the people who will use the system

05

Support and maintenance

Software and networks are not finished on the day they go live. Maintenance is an agreement, not an obligation.

  • Security patches and dependency updates
  • Uptime and backup monitoring
  • Small content and feature changes
  • A monthly report on status and recommendations

Have a project? Get in touch.

Describe what you need in a few sentences. We reply directly, no automated messages.

Send an enquiry

or write to

info@quantumcode.hr