EditandoIdeas

Consulting

Before we build, we design the technology decision.

Diagnosis, product discovery, architecture, and a roadmap that takes uncertainty out of a project before it starts costing money.

What it solves

Five situations where quoting a build is guesswork.

  • The idea is still fuzzy

    There is a clear business opportunity, but nobody can turn it into scope. Every vendor quotes something different because every vendor understood something different.

  • A legacy platform is holding the business back

    The system runs the operation and simultaneously prevents changing it. You can neither switch it off nor keep going like this.

  • Technical debt is showing up on the calendar

    What used to take a week now takes a month, and nobody can explain exactly why.

  • You have to choose a technology or a vendor

    Three proposals that cannot be compared to each other, and no independent basis for deciding.

  • You are building without architecture

    The team is shipping, but every decision is made in the moment and none of them get written down.

Services

What consulting covers.

  • Product discovery: from business problem to the smallest defensible scope.
  • Diagnosis of an existing platform or process.
  • Solution design and architecture, with explicit boundaries.
  • Build vs. buy evaluation, on criteria rather than preference.
  • Phased technical roadmap, with dependencies and risks.
  • Audit of code, delivery process, or an AEM implementation.
  • Technical governance and documentation, so judgment stops depending on one person.
  • Assessment of real applied-AI opportunities — including concluding there are none.

Format

What a consulting sprint looks like.

A bounded period, named participants, and a written deliverable. Not open-ended meetings until someone gets tired.

  1. Framing

    We agree on the question to answer and what would make the answer useful.

  2. Immersion

    Conversations with business, operations, and engineering. A review of what already exists.

  3. Options

    Two or three paths on the table, with cost, risk, and what each one closes off.

  4. Recommendation

    A reasoned decision, not a menu. With what supports it and what would invalidate it.

  5. Handover

    Document, walkthrough with the team, and answers to the questions that come up afterward.

Deliverables

What you walk away with.

Depending on agreed scope. Never all of them at once: a deliverable nobody will read is not a deliverable.

  • A map of the problem and the people involved.
  • A clickable prototype when the doubt is about product, not technology.
  • Solution architecture with decisions on record.
  • A prioritized initial backlog.
  • A risk register with mitigations.
  • A phased estimate with stated assumptions.
  • A phase plan with exit criteria.

Who takes part

Without these people, the result falls short.

Consulting is not a technology exercise: half the answers live in operations.

  • Whoever owns the budget and can close the scope.
  • Whoever knows the real process, not the documented one.
  • Whoever will maintain the system afterward.
  • When relevant: legal, security, or compliance.

The recommendation does not oblige you to hire us for the build.

If the answer is buy rather than build, we say so. If the best path is your internal team, same. A consulting engagement that can only end in a project of our own is not consulting — it is a sales proposal with a different name.

Generative AI

We use generative AI throughout. The decisions stay human.

Generative AI lets us deliver sooner, at higher quality, with better results — because it frees up hours of mechanical work and returns them to what actually decides whether a project succeeds: understanding the problem and reviewing what got built. It does not choose the architecture, sign off on security, or answer for delivery.

  • More value per project: the time not spent on repetitive work goes into solving your business problem.
  • Less time to a first version: a conversation becomes scope, risks, and a prototype in hours instead of weeks.
  • Early prototypes your team can actually click through before you commit budget.
  • Better quality: assistance with code, tests, and documentation, with more coverage than fits in the same schedule.
  • Better results: more iterations on what matters, because each pass costs less effort.
  • Intelligent features inside the product only when they earn their place.
  • Mandatory human review of architecture, security, and quality before every release.

Let's design the solution.

Start by understanding the problem. Scope comes after that.

Let's design the solutionExplore our capabilities