The method

We write the plan before we start the press.

A failed project is almost never failed for technical reasons: it fails because nobody wrote down what was being built. This is the order the studio follows, without exception.

Timetable

Departure: Analysis
Stations: 7 steps
Switch: Written and signed scope
Terminus: Evolution — never-ending

The railway

Seven steps, in this order.

Station 01 / 07Analysis

Analysis

We look at how you really work: documents, approval flows, friction points, your teams’ vocabulary.

Scoping

Written scope, ranked priorities, what goes into the first version and what waits. Nothing starts without agreement on this document.

Design

Screens are drawn and approved before the first line of code. You see the tool before it exists.

Development

Built in short cycles. At the end of each cycle, something real is delivered and usable.

Testing

Your real cases, your real data, your real users. We fix before going live, not after.

Deployment

Go-live, migration of existing data, team training, and a period of close support.

Evolution

The tool follows your company: fixes, improvements, new features when the need arises.

The railway

Seven steps, in this order.

You know at every moment where yours stands and what comes next.

01
Analysis
We look at how you really work: documents, approval flows, friction points, your teams’ vocabulary.
02
Scoping
Written scope, ranked priorities, what goes into the first version and what waits. Nothing starts without agreement on this document.
03
Design
Screens are drawn and approved before the first line of code. You see the tool before it exists.
04
Development
Built in short cycles. At the end of each cycle, something real is delivered and usable.
05
Testing
Your real cases, your real data, your real users. We fix before going live, not after.
06
Deployment
Go-live, migration of existing data, team training, and a period of close support.
07
Evolution
The tool follows your company: fixes, improvements, new features when the need arises.

An agreement with two signatures

Nothing starts until the scope is signed by both sides.

01The studio commits

What you receive every cycle

A link to a real, usable version, with the list of what was done and what comes next. No progress report without working software behind it.

Signed · AkisRead and approved

02You commit

What we ask of you

A contact who knows the trade and can make decisions, and access to your real documents. That’s all, and it’s essential: a custom tool is built with the people who will use it.

Signed · YouRead and approved

The workshop

The tools the studio masters.

Tools don’t make the project, but they decide what we can promise you — and your teams will find another provider for each of them if they ever switch.

akis · workshop

Interfaces

Next.js
React
TypeScript
Tailwind CSS
React Native

Engines

Node.js
Python
PostgreSQL
REST & real time

Data & AI

PostgreSQL
Document extraction
Language models
Analysis & decision

Operations

Vercel
Monitoring
Backups
SMPP / SMS gateways

Scoping is the first step, and it’s free.

The first conversation is to understand your need and tell you frankly whether there is a project, what it involves, and in what order to tackle it. Pricing comes after, once the scope is written.

Start scoping akis.med@gmail.com

Djibouti · remote · reply within 48 h