Skip to content

Menu

Four things we build, and how long they take

Each card has a small demo to try, the typical timeline and what you get at the end. A project often combines two.

We fix the price before we start. The first conversation is free.

Business apps

Typical timeline:8–12 weeks

For people who work away from the office: enter data, take photos, get the customer's signature and receive alerts on the phone, even where there's no signal.

Try it here

Simulation of a field-work app: job reports logged without signal wait on the phone and reach the ERP on their own when the connection returns.

Job reports

All sent
Online
  • Greco LogisticaSent#1043 · Site survey
  • Colombo SpaSent#1042 · Installation
  • Ferri ImpiantiSent#1041 · Maintenance

Phone connection

Try it: take the phone offline, log two jobs, then go back online.

ERP log

Illustrative demo with sample data: nothing is saved.

The problem
  • Job reports and orders taken on paper, then retyped at the office
  • Data that reaches the office days late, and with errors
  • Where there's no signal, work stops
What you get
  • One app for iPhone and Android
  • Works without signal and sends the data as soon as it's back
  • Barcode reading, photos, signature and GPS location
  • Phone notifications and publishing on the App Store and Google Play
What changes
Data in the ERP a few seconds later, even if the phone had no signal.
Stock updated with every movement, not at the end of the week.

Custom web business software

Typical timeline:6–10 weeks

The business software that replaces the shared file: data and steps in one place, with different permissions for each person. It opens in any browser.

Try it here

Simulation of web business software: each role sees only the modules and data it needs, and every change is written to the log.

View as

  • Orders
  • Customers
  • Inventory
  • Invoices
  • Reports

Order 2025-0142

Processing
Customer
Rossi Srl
Amount
€12,480
Margin
31%
Parcels
24 parcels, shelf B3

Change log

  1. 08:12 · Sales · order created

Illustrative demo with sample data: nothing is saved.

The problem
  • Ten versions of the same Excel file, none of them current
  • Information scattered across email, folders and the ERP
  • Anyone can change anything, and nobody knows who did
What you get
  • Custom business software that opens in any browser
  • Roles and permissions for every team member
  • Connected to the software you already use, your online shop and your bank
  • Change log and automatic backups
What changes
One archive, updated as people work.
Approvals in one click, with a record of who approved what.

Business dashboards

Typical timeline:3–6 weeks

Indicators that update themselves from your data, an alert when something goes out of range, and reports that go out without anyone filling them in.

Try it here

Simulation of a logistics dashboard: pick a period and move the alert threshold to see which periods fall below target.

Period

Logistics dashboard, demoRefreshed every 5 minutes
Revenue
€596,000+11% vs the previous period
Orders fulfilled
3,840+9% vs the previous period
On-time deliveries
90%
On-time deliveriesthreshold 88%

3 periods below the thresholdalert sent to the logistics manager

Illustrative demo with sample data: nothing is saved.

The problem
  • Half of every Monday spent copying numbers into reports
  • Decisions made on data that is weeks old
  • Problems discovered when it's too late
What you get
  • Real-time indicators connected to your data
  • Automatic alerts when a value goes out of range
  • PDF reports that send themselves, every week
  • Access from desktop and smartphone, with permissions
What changes
The report is always up to date and nobody has to fill it in.
An anomaly reaches you as an alert the same day.

AI automation

Typical timeline:2–4 weeks

Programs that read emails and documents, sort requests and prepare draft replies. The decisions that matter always go through a person.

Try it here

Simulation of an AI agent that reads the inbox, recognizes quotes, orders, complaints and spam, and prepares the next step. Replies to customers go out only after you approve them.

Email agent, demo

Inbox4

  • Rossi Srl, PurchasingQuote

    Quote request: 200 units of item B-114

    Reply draft ready
  • Colombo Spa, LogisticsOrder

    Confirming order no. 5521 for Thursday

    Logged in the ERP
  • Greco LogisticaComplaint

    Goods arrived damaged, photos attached

    Ticket opened for quality control
  • Prizes & WinningsSpam

    You won a €500 voucher! Click now

    Archived

Illustrative demo with sample data: nothing is saved.

The problem
  • Inboxes full of near-identical requests
  • Hours spent copying data from PDFs and documents
  • Customers waiting until the next day for an answer
What you get
  • AI assistants that know your documents and the way you work
  • Email triage and replies, with drafts for you to approve
  • Data read automatically from PDFs, invoices and orders
  • Human sign-off on every important decision
What changes
Draft replies ready in a few seconds, even at night.
Repetitive requests close on their own, and the rest arrive already sorted.

Your Excel file, turned into business software

Drag the slider: duplicate rows, errors and dates written three different ways disappear. What's left is a tidy app the whole team can use.

Illustrative example: an Excel order sheet with a duplicate row, two #REF! errors and dates typed in different formats. After cleanup the data is consistent; the finished software adds search, filters and a clear status for every order.

From the first meeting to software in use

A version to try every two weeks and a price fixed before we start. Pick a service to see the typical timeline.

Timeline by service

Typical duration
8–12weeks
First demo
week 4
Cycle
2 weeks

Business apps. Process analysis: 1 week, Prototype: 1 week, Development: 8 weeks, and Launch: 2 weeks. Typical duration 8–12 weeks, then ongoing support.

  1. 01

    Process analysis

    We map the process with the people who run it every day and estimate how much time you get back.

    DeliverableProcess map and fixed-price quote

  2. 02

    Prototype

    Clickable screens to try with your team before we write the code.

    DeliverableApproved clickable prototype

  3. 03

    Development

    Two-week cycles, each ending with a test on your real data.

    DeliverableA working version every two weeks

  4. 04

    Launch

    Final testing, moving your data over and training the people who will use it.

    DeliverableSoftware in use and user guide

  5. 05

    Support

    We keep an eye on the software, then fix and improve it based on real use.

    DeliverableOngoing assistance and updates

Run the numbers on your case

Five numbers, and you see how many months an automation takes to pay for itself.

ROI calculator

Let's start with the process that costs you the most time

Describe it in two lines. We reply within one working day with a first idea.