Sound familiar?

Companies with a development teamDevelopment track

  • You bought AI coding tools, but only about half the team actually uses them.
  • Development got faster, and you're not sure quality kept up.
  • You haven't decided how the development team should change.

On the development track we look at repositories, deployment and code review, then design where AI fits, the rules and the security settings.

Companies without a development teamBusiness track

  • You know you should use AI, but not where to start.
  • You want the work people repeat by hand every day to happen on its own.
  • Nobody inside the company can judge the technology and decide.

On the business track we look at how work flows and what gets repeated, then decide task by task between existing tools, SaaS or something built.

If both fit, we run the two tracks together under one contract.

Talk to us

If even one of these fits, start with a three-week advisory.

In three weeks, we work out what to change with AI and how

We come to your office, watch how the work gets done and decide together.

Sample 90-day roadmap for a fictional company, Acme Corp. Each task shows an owner, a schedule over three 30-day blocks, and the metric that will show whether it worked.
The 90-day roadmap you get in week three (sample)

How the three weeks go

  1. Week 1What to change

    We listen to the people doing the work and watch how it gets done, then rank the tasks where AI could help.

    You get
    Current-state assessment, sample for a fictional company
    Current-state assessment
  2. Week 2How to change it

    In a workshop we decide together what changes and what stays, and settle tools, security and cost.

    You get
    Target design, sample for a fictional company
    Target design
  3. Week 3What comes first

    We define the metrics and the first pilot, and present a 90-day roadmap to your leadership.

    You get
    Metric definitions, sample for a fictional companyFirst pilot scope, sample for a fictional company90-day roadmap, sample for a fictional companyLeadership briefing, sample for a fictional company
    Metric definitions, first pilot scope, 90-day roadmap, leadership briefing

You can stop after week one

Hear the week-one findings and stop there if you like. If you don't need AI right now, the assessment will say so.

After the advisory

Build (AX solution)

We install it on your servers following the design. If you move on to a build, the advisory fee comes off the build contract.

See the AX solution →

Monthly advisory

While you work through the 90-day roadmap, we meet every two weeks to review it with you.

AI workshops

Hands-on sessions of four or eight hours, up to ten people at a time. Your team picks the material.

Terms

  1. 01One engagement per company, contracted by track: development or business.
  2. 02We do the work on-site at your company.
  3. 03You can stop after the week-one findings report.
  4. 04If you move on to a build, the advisory fee comes off the build contract.
  5. 05We don't ask for source code or data up front. We take them only if you want us to.
  6. 06Pricing depends on scope and is covered in the consultation.

FAQ

Can we get just the assessment?

Yes. Hear the week-one findings and stop there if you like. You keep the current-state assessment.

Do we have to hand over our source code first?

No. The development track can run on a new project. Whether to show us an existing repository is up to you.

What if we don't have a development team?

That's what the business track is for. We look at how your team works and what tools it uses, then decide task by task between existing tools, SaaS or something built.

What if several departments are involved?

It's one engagement per company. We decide together in week one which department to start with.

How much does it cost?

It depends on the number of tracks and the scope. We cover it in the consultation.

Talk to us

Tell us your company size and the tools you use now, and we'll reply with which track fits.

hello@mvpit.dev
Headcount
Tools in use