Let's Talk

// AI CREATION SPRINT

From an idea to a working tool.

A two-week sprint to teach your team how to turn real operations problems into digital solutions using AI, no-code and vibe coding.

// THE PROBLEM

Talking to AI was only the beginning.

Artificial intelligence is already part of the company routine. It helps write, summarize, research and organize ideas.

There is still a gap between chatting with an AI and using these new tools to build something.

Meanwhile, teams keep dealing with spreadsheets that are hard to maintain, manual controls, scattered information and processes that never become a priority for a large technology project.

Today, many of these problems can be solved with smaller tools, created quickly and shaped around the reality of each area.

That is the passage this sprint conducts: leaving one-off AI use and arriving at a concrete solution.

// THE IDEA

AI does not need to live inside the system. It can be the tool used to create it.

// THE SPRINT

This is not an AI class. It is an idea put into practice.

For two weeks, Matilha works alongside a team inside the company.

First, we present what is possible, the tools and the necessary care. Then we investigate the area's problems and choose an opportunity with real impact and the right complexity.

From that choice, we design, build and test a first version of the solution.

The team takes part in the whole process. Besides receiving a working tool, they understand how an idea becomes a product and gain the repertoire to create the next ones.

We teach while we make. We make it together so the team can continue.

// AN EXAMPLE

Picture an HR team.

HR needs to know which people are allocated to each project, who is available and when an allocation will end.

The information exists, but it is spread across spreadsheets and messages. The team knows the problem better than anyone, yet does not imagine itself creating a solution.

During the sprint, that need can become a tool with:

  • people by project
  • availability
  • roles and skills
  • start and end dates
  • filters
  • indicators
  • allocation updates

The board does not need artificial intelligence to work. AI is used to help the team define and build the board.

The people who live the problem start taking part in creating the solution.

// TWO WEEKS

How the two weeks work.

  1. Week 1

    Understand and decide

    1. Learn

      We present what can be created with AI, no-code and vibe coding, plus the limits, risks and care involved.

    2. Find

      We map repetitive tasks, manual controls, bottlenecks and problems in the area.

    3. Choose

      We prioritize an opportunity based on impact, effort, available data and feasibility.

    4. Design

      We define users, flow, information, screens and essential functions.

  2. Week 2

    Build and put it to work

    1. Create

      We build the first version together with the team.

    2. Test

      We put the tool in front of users and watch how they use it.

    3. Adjust

      We fix the main issues and refine the flow.

    4. Deliver

      We make the solution available, train the people responsible and organize the next evolutions.

// WHAT YOU LEAVE WITH

A first solution and the capacity to create the next ones.

  1. a prioritized problem
  2. a working MVP
  3. a flow validated with users
  4. a configured tool
  5. essential documentation
  6. an improvement backlog
  7. guidance for maintenance
  8. a trained team
  9. opportunities for the next projects

We do not deliver a finished system in two weeks. The promise is a working MVP with scope defined during the sprint.

// BY AREA

The first project changes shape. The method stays the same.

  • HR

    Allocation board, onboarding, training management or review tracking.

  • Operations

    Process control, internal requests, project tracking or incident management.

  • Finance

    Approval flows, document organization, controls and management boards.

  • Procurement

    Supplier records, order tracking and approval processes.

  • Sales

    Opportunity qualification, proposal organization and deal tracking.

  • Support

    Information hub, request triage and case tracking.

  • Startups

    Idea validation, internal tools, automations and first MVPs.

// THE FIRST PROJECT

We start small to create a real change.

The first project should solve a specific problem, have identifiable users and be testable within two weeks.

The goal is not to replace an ERP or create a critical system for the whole company.

The goal is a first concrete win: a useful tool, built quickly, able to show a new way of working.

// CARE

Creating fast also takes judgment.

Before choosing the solution, we review the data involved, access, privacy, integrations, costs and maintenance.

In larger companies, the technology team can join as a partner for security and governance, even if another area leads the project.

The tool is chosen after the problem and the requirements are understood.

// LET'S TALK

Which tool would your team create first?

Bring a real operations problem.

In two weeks, Matilha helps your team turn that need into a working MVP, and shows how to start the next ones.

Talk about the sprint

// OTHER SERVICES