How we work

You know what you get at every stage before you pay for it

Before we start, you want to know what working together looks like, who your contact will be and what happens when the scope changes. A project at Codari goes through five stages, from a conversation about the problem to launch and maintenance. At every stage you talk to the people who write the code, and the scope and every change to it are agreed in writing.

Describe your project
A team discussing a project over laptops

What does a project look like, step by step?

  1. 1

    Discovery and requirements

    We start from the problem, not a feature list. How we run requirements analysis

    You get: a description of the project's goal, its users and constraints.

    We need from you: a description of the problem, examples of your current process and access to the people who know it.

    A conversation about project requirements
  2. 2

    Scope and estimate

    We agree what goes into the first version and what waits for later ones.

    You get: an estimate for the first version and a list of things deliberately postponed.

    We need from you: a decision on what's truly essential.

    A team agreeing the project scope
  3. 3

    Prototype or MVP

    We test assumptions on something clickable before big decisions are made. What an MVP is

    You get: a clickable prototype or a first working version.

    We need from you: feedback from real users.

    Sketching a prototype on a whiteboard
  4. 4

    Sprints

    We work in short cycles: every two weeks we show a working piece in a short meeting, so fixes come early. Key stages of software development

    You get: visible progress on working software.

    We need from you: your presence at reviews and quick decisions.

    Developers working on code
  5. 5

    Launch and maintenance

    We launch, monitor and keep developing. We offer a maintenance package together with the implementation contract.

    You get: the application in production, administrator access and user manuals.

    We need from you: someone on your side who owns the solution.

    A handshake after a project launch

When the scope is unclear or stakeholders have different visions, we start with a short workshop that turns them into one shared description. How it works: MVP workshops.

What principles do we work by?

You talk to the people who write the code

Your contact is a project lead who knows the code, not a middleman.

Scope in writing

The scope is written down, and every change is a separate agreement with a clear impact on timeline and budget.

We say it plainly

When something is a bad idea, or a cheaper solution would do, you'll hear it from us.

Progress on working software

We regularly show working pieces, not slides.

What happens when a project goes worse than planned?

Problems come up at the sprint review, not at final acceptance, and that's where we discuss them. If the scope grows, we show the impact on timeline and budget before we start work on the change, and you decide whether to go ahead.

How do we bill?

We're flexible here and match the model to the project.

ModelHow it worksWhen to chooseRisk and how we limit it
Fixed priceScope and price agreed upfrontClear and stable scopeScope changes need renegotiation, so we describe each one with its cost impact
Time and materialYou pay for the actual time workedChanging scope, a product under developmentLess predictable budget, limited by a cap and regular reporting
MilestonesYou pay after each stage is acceptedThe scope can be split into stages with clear acceptanceDisputes over whether a stage is accepted, so we write down acceptance criteria upfront
SubscriptionA fixed monthly fee for maintenance and development after launchThe application is live and needs ongoing careUnused hours, so we size the subscription to real needs
Dedicated teamA fixed monthly rate for the teamA long project, continuous developmentA fixed cost regardless of workload, so we size the team to the real scope

How do you prepare to work with us?

A description of the problem, examples of your current process and who will use the solution are enough. You don't need a specification, it's created during analysis. A practical list of questions to ask yourself before the call: how to prepare for working with an IT company.

FAQ

Yes. We describe every change with its impact on cost and timeline, so you decide with full information.

A working application in production, administrator access and user manuals. Together with the implementation contract we also offer a maintenance package, so before launch you know what ongoing care will cost.

A project lead who knows the code, not someone who only handles client communication.

Yes, from Łódź, Poland, with companies across Europe, in the Central European time zone.

Let's talk

Let's build
something great.

Do you have a vision you want to bring to life? Or perhaps you need support in growing your business? Trust the experts at Codari!

What do you gain?

  • IT solutions tailored to your needs.
  • Direct support from our experienced specialists.
  • Ideas that drive your success.

Your journey to digital transformation starts here!

0/1000

privacy policy.