IT consulting before you invest

Code and tech-debt audits, architecture and project plans that show what to do first.

When you need a second opinion

  1. New features take longer with every release

    An audit shows where the technical debt is and what to fix first.

  2. Key developers have left, and nobody knows the system well

    We review the code and the architecture and describe where the product stands.

  3. You're about to start a project and need a realistic plan

    We estimate the scope and prepare a plan before you commit a budget.

Tell us where your product stands.

Discuss your project

Four areas of consulting

Choose one area or combine several.

  • Code and tech-debt audit

    What state the code is in, where the risks are and what to fix first.

  • Architecture and technology choice

    An architecture and a stack that fit your product and your team.

  • Project estimate and plan

    Scope, stages and risks, so you know what you're committing to.

  • Digital tools for small businesses

    Which services to connect: a website, online booking, a CRM, automation.

How a project runs

  1. Discussion
  2. Estimate
  3. Design
  4. Development
  5. Testing
  6. Launch
  7. Support

How we work with you

  • NDA before we discuss details

    We sign an NDA before you share code, documents or plans.

  • Your accounts and data stay with the project team

    Credentials and data are available only to the people working on your project.

  • Estimate and scope before work starts

    We agree on both before we begin, with no hidden charges.

  • One manager and a weekly report

    You talk to one person and get a progress report every week.