How we work

Clear stages, clear responsibilities.

This is how we work on a website, an online store or a platform: at every stage you know what you get, what you decide and what comes next, from the first call to ongoing development.

You always know where your project stands. Five stages, each ending in a result you see and approve.

01 / 05

Definition

Together we define what the product has to do, who it is for and what goes into the first version.

You getRequirements, flows and an estimateApproved by you

Who does what, at every stage. Responsibilities are set from the start, so there are no grey areas.

  1. 1Definition

    We
    We talk to your team, analyse the current flows and systems and prioritise the requirements.
    You
    You explain the goal and give us access to the right people and systems.
    You get
    Prioritised requirements, flows and an estimate.
    You decide
    What goes into the first version, and the budget.
  2. 2Design

    We
    We design the interface on the approved flows and test it on a prototype.
    You
    You give feedback on the prototype and the screens.
    You get
    A clickable prototype and final screens.
    You decide
    You approve the design before development.
  3. 3Development

    We
    We build in iterations, test and publish each version to the test environment.
    You
    You check the versions and answer questions.
    You get
    Working versions in a test environment.
    You decide
    You approve each iteration or ask for changes.
  4. 4Launch

    We
    Final testing, data migration, setup, release and training.
    You
    You prepare the final content and the access we need.
    You get
    A live product, training, access and documentation.
    You decide
    You approve the launch.
  5. 5Ongoing development

    We
    We monitor, fix and build improvements.
    You
    You set the priorities with us.
    You get
    Improvements delivered by the agreed priorities.
    You decide
    What comes next and the support level.

Three collaboration models. We choose the model by how stable the scope is, not by our preference.

  • A good fit for you

    Fixed-price project

    Fits when
    The scope is clear and stable: a website, an online store or a well-defined first version.
    How it works
    We agree on the deliverables; price and timeline are fixed on that basis. Changes are estimated separately, before they are made.
    What you control
    You know the total cost and what you get from the start.
  • A good fit for you

    Dedicated team

    Fits when
    The product keeps evolving and priorities change often.
    How it works
    A team works on your product from a priority list you set with us. The cost is based on the team’s capacity.
    What you control
    You decide the priorities at every iteration.
  • A good fit for you

    Ongoing development and support

    Fits when
    The product is live and you need improvements and someone to watch over it.
    How it works
    The contract sets what is monitored, how requests are prioritised and how quickly we step in.
    What you control
    You see what was done and what comes next.

How we estimate the budget. No catalogue prices: the estimate starts from what the product has to do.

  1. We split the project into features

    Each flow becomes a list of features you can read and discuss.

  2. We estimate each feature

    You see where each part of the budget comes from.

  3. We separate the first version from what can wait

    You launch what brings value sooner and postpone the rest.

  4. You get the estimate in writing

    With the assumptions behind it, so you know what could change it.

What changes the effort

Pick what your project needs:

Relative effort: small · A well-defined first version

Illustrative, no prices. You get the real estimate in writing after the first call.

After launch. What is monitored, how it is prioritised and who is responsible for what, all set in the contract.

  • What we monitor

    Uptime, errors, forms and payments, as relevant.

  • How we prioritise

    Together, by business impact and urgency.

  • What support covers

    Fixes, security updates and small improvements, as agreed in the contract.

  • Response times

    Set in the contract, depending on how critical the product is.

  • Third-party services

    Hosting, payments, APIs: we agree who is responsible for each.

Questions about working together. Kick-off, preparation, takeovers and support.

Didn’t find your answer?

Write to us and we’ll answer your exact question.

Ask a question
How does the collaboration start?

With a call about your goal and feasibility. Then comes definition: requirements, flows and a prototype. Development starts once you approve the estimate and the plan.

What should I prepare?

A description of the problem, examples you like and access to the systems you use: CRM, ERP, payments. If you don’t have them all, we sort them out together.

Can you take over an existing project?

Yes. We start with an audit of the code and data, then propose the right path: build on what exists, modernize in stages or migrate to a new system.

What happens after launch?

We take care of maintenance: we monitor the product, fix issues and keep improving it, with priorities we set together. The support level and response times are agreed in the contract.

Let’s start with the first call. Goal, feasibility and the next step. Write us a few lines about your project.

What happens next

  1. You send the requestA few lines about what you want to build.
  2. We get in touchWe clarify the details and book the call.
  3. The first callGoal, feasibility, next step.

Prefer to reach us directly?

info@makeit.md +373 69 593 336

What should we build? (optional)

Validating a new product? Write “new product”.

When would you like to start? (optional)

Fields not marked “optional” are required.

We use your data only to reply to you. Details in our Privacy policy.