Digital systems for growth · Spain

Build the systems your business needs to grow.

We simplify the work behind your business so your team can move faster, serve customers better and keep growing.

Automation, AI, integrations and custom software—only where they genuinely help.

A practical path to growth Understand · simplify · build · compound

Friction removedCapacity created

Start

Understand

The real workflow, mapped.

First release

Useful system live

Solve the core bottleneck first.

Value returned

More capacity

Less manual work, better flow.

Keep improving

Growth compounds

Learn from what really happens.

This probably shouldn’t be manual.

These are usually not people problems. They are process and system problems.

Show us your workflow

We don’t start with technology.

We start by understanding the problem and how the work happens today. Then we remove unnecessary steps, redesign the workflow and choose the technology that makes sense.

  1. 01

    Understand

    Map what happens today.

  2. 02

    Analyse

    Find the friction, risk and cost.

  3. 03

    Simplify

    Remove work that does not need to happen.

  4. 04

    Design

    Define the better workflow.

  5. 05

    Build

    Implement the smallest useful solution.

  6. 06

    Improve

    Measure what happened and improve from reality.

The solution depends on the problem.

Sometimes the answer is a simpler process or better use of a tool you already have. When something needs building, it may involve:

  1. 01

    Automation

    Useful when a task is repetitive, predictable and follows clear rules.

  2. 02

    AI

    Useful when work involves reading, classifying or drafting from text, documents and enquiries—usually with human review.

  3. 03

    Integrations

    Useful when people copy information between systems or multiple tools disagree about the same data.

  4. 04

    Web and applications

    Useful when customers or employees need a clearer interface for completing a workflow.

  5. 05

    Custom systems

    Useful when existing software almost fits, but the missing part is central to how the business works.

How we’d solve it

A company receives dozens of enquiries every day. Someone reads each email, categorises it, copies the details into the CRM and creates follow-up tasks.

Before

  1. 01EmailThe enquiry arrives as unstructured text, so someone must interpret it.
  2. 02EmployeeA person pauses other work to read, sort and route every message.
  3. 03SpreadsheetDetails are copied into a temporary tracker that can drift out of date.
  4. 04CRMThe same data is entered again, introducing delay and mistakes.
  5. 05TaskA follow-up task is created manually and can be missed.
  6. 06ReplyThe response waits until every earlier hand-off is complete.
What is actually broken

The inbox is not the problem. The repeated hand-offs are.

After

  1. 01EnquiryOne structured intake captures the information the workflow actually needs.
  2. 02ClassificationRules or assisted review classify the request consistently at arrival.
  3. 03CRMValidated details move into the CRM once, without retyping.
  4. 04PriorityAgreed signals surface urgent work first instead of relying on inbox order.
  5. 05TaskThe right follow-up is created automatically with the context attached.
  6. 06Human reviewA person handles the judgement call, not the copying between tools.

The goal is not to remove humans.The goal is to remove unnecessary manual work.

Problems we’ve turned into working products

Real systems designed and built around a specific problem.

Shopify checkout rules

CheckoutControl

Problem
A Shopify store needs payment and delivery methods to change according to the order, but that logic can become brittle and difficult to manage.
What we built
A shared rule editor connected to Shopify Functions for supported payment, delivery and Cash on Delivery flows.
What it solves
It keeps checkout logic understandable, testable and changeable in one place.
See the project
CheckoutControl checkout-rule artwork

Private Android journal

BeachLog

Problem
Beach visits, photos, notes, maps and practical details need one private home—not another social feed.
What we built
An offline-first Android journal for beaches, visits, photos, maps, packing lists and recaps.
What it solves
It keeps a personal beach history together without requiring an account or cloud sync.
See the project
BeachLog map screenBeachLog saved beaches screenBeachLog visit history screen

Commander deck analysis

Moxscore

Problem
A 100-card Commander decklist shows the cards but not the balance or structure behind them.
What we built
A browser-based deck analyser with a health score, role breakdown, mana curve and deterministic guidance.
What it solves
It turns a decklist into understandable signals without relying on a black-box verdict.
See the project
Moxscore deck analysis interface
P

8digits is led by Peter. You speak directly with the person who will help diagnose the problem and shape the solution.

Start with the problem

A few things we believe

  1. 01

    Not every problem needs AI.

  2. 02

    A bad process automated is still a bad process.

  3. 03

    Another software subscription will not fix a broken workflow.

  4. 04

    If people enter the same information twice, something is probably wrong.

  5. 05

    Your website is part of your business system, not just a brochure.

  6. 06

    The simplest useful solution usually wins.

Problems worth fixing

Practical thinking about manual work, business systems, AI, automation and better digital workflows.

View all articles
Reduce unnecessary manual labour

The Hidden Cost of Unnecessary Manual Work in Small Businesses

A client once ran Salesforce for the sales team and Azure for manufacturing. When they added HubSpot to get a clearer view of everything, the new system did not talk to the old ones. Every day people spent hours recreating the same data from one platform into another. When a deal finally reached manufacturing it […]

Read article
AI Implementation is more important than the tools.

AI tools don’t fail. The workflow around them does.

Most AI projects stall not because the model is bad, but because it was dropped into a broken process and expected to absorb the chaos. Here’s what’s actually going wrong – and what to fix first. Every week I talk to a founder or ops lead who says some version of the same thing: “We […]

Read article

Have a process that shouldn’t work the way it does?

Show us how it works today. We’ll help you identify the bottleneck and figure out what a better solution could look like.

  • One paragraph is enough.
  • You do not need a specification.
  • English or Spanish is fine.
problem intake · step 1/2
01 · Problem02 · Contact
Tell us about the workflow

Prefer to talk? Book 20 minutes