[01] Development and automation
Nothing by hand. We build the software that does it.
We reply on WhatsApp, usually within the hour.
No form. No sales demo.
- Quotes generated from your catalogue
- Follow-ups sent without anyone remembering
- Stock in sync between the warehouse and the site
- Supplier invoices entered on their own
- Orders pulled out of the customer portal
- Site hours reported straight from the field
- Team scheduling that recalculates itself
- Bank statements reconciled every morning
- A signed quote that turns into an invoice
- The same customer questions handled without you
- Files assembled from your email attachments
- Deliveries tracked without calling the carrier
[02] Before, after
What changes, in writing.
- Quotes that double along the way
- The signed amount is the invoiced amount
- "Where are we?" with no answer
- A demo every Friday
- Nobody picks up after delivery
- A breakdown at 3am gets you Loïs or Pascal
- Leaving costs more than staying
- You leave with everything, whenever you want
Firm price, firm date, signed before we write a line. The code is yours.
[03] Two ways to do this
Ready-made, or made for you.
Running this week
Astar Systems
Official Meta Tech Provider
Pilot and Sales, on a universal API that sends each request to whichever model fits it. Sales wires into the whole Meta suite. It installs in two minutes. If a product already solves it, take the product.
Built around you
Zippytal
When no product fits, we build the one that does. On your data, your way. It belongs to you.
[04] What it costs you
Your business runs. Your operations don't.
None of this is a technology problem. It is a systems problem, and it grows every week.
Quotes retyped by hand from one tool into another
A typo reaches the customer, and you are the one who finds it.
Prospects lost because nobody followed up
They bought elsewhere. You will never know which ones.
Three tools holding the same data, never agreeing
Nobody knows which one is right, so somebody phones to check.
One person who knows how all of it works
They take a week off and everything waits for them.
[05] What we build
Four engines.
An engine is software that takes one repetitive job and does it for you, every day, without being asked. The same four turn up in every company. We build each one on your data. Never a template with your logo on it.
Acquisition
We find them. You get them warm.
- Replaces
- Prospecting by hand. A CRM full of dead rows.
- Plugs into
- Your CRM, your inbox, LinkedIn, WhatsApp.
Qualified conversations. Not a list you dread opening.
Sales
Your answers, your tone. Follow-ups that go out.
- Replaces
- Forgotten follow-ups. Quotes retyped by hand.
- Plugs into
- WhatsApp, email, your quoting tool, your calendar.
Nobody waits. Nothing falls between two tools.
Customer service
The routine handled. The rest reaches you with its context.
- Replaces
- The same forty questions answered by hand, every week.
- Plugs into
- WhatsApp, your helpdesk, your order and delivery data.
Your team only sees what needs a person.
Operations
Legacy software, driven the way a person would.
- Replaces
- Copy-paste between the ERP and the spreadsheet.
- Plugs into
- Legacy software, closed portals, bank dashboards. Through the interface itself.
The work gets done. Nobody does it.
[06] Concretely
If a person can click it, we can automate it.
Most automation gives up when a system has no way in. Ours drives the screen instead: it logs in, fills the fields, checks the result, writes down what it did. The same steps your assistant takes, minus the four hours.
- 01Pulling orders out of a supplier portal with no export
- 02Filing entries into an ERP older than REST
- 03Getting statements from a bank with no business API
- 04Moving data between two vendors who refuse to integrate
[07] Selected work
What we built. What it did.
Automation is not all we build. Mobile apps, platforms, sites, engines that run overnight. What they share is that each one started at zero and ended up in your name.
SwimKlub
Our own moneyMobile app + management platformCo-built · design + build
A mobile training app for adult swimmers, built with Wissam-Amazigh Yebba, a French international selected for the Paris 2024 Games. Behind it, a back office, a web console for the coaches, coaching management and training-camp scheduling. Every session is written from a single number: your 400m time.
16
video testimonials
swimklub.fr, 2026
Astar Systems
Our own moneyOfficial Meta Tech ProviderAI products + universal APICo-built · product studio
Our sister studio. Pilot and Sales, on a universal API that sends each request to whichever model fits it, with Sales wired into the whole Meta suite. Astar is an official Meta Tech Provider. We built the product company, which is the clearest argument that we can build yours.
trader-lab.com
Web platformDesign + build + launch
A trading education platform. From nothing to a live product and an audience, without buying a single ad.
2 000
users
Zippytal, self-reported
0 €
ad spend
Zippytal, self-reported
AI Code Academy
Platform + paymentsFunnel + platform + payments
A cohort programme with the funnel, platform and payments built end to end.
10 k€
post-launch
Zippytal, self-reported
[08] How it goes
Four steps, and you own the last one.
- 01
A call
Twenty minutes on WhatsApp. You describe the work. We tell you whether it is worth automating, and what it costs.
- You
- Twenty minutes on WhatsApp.
- We
- A firm price and a firm date.
- 02
A prototype
Not a slide deck. Something running on your real data. You judge instead of imagining.
- You
- You judge it on your own data.
- We
- Something that actually runs.
- 03
Production
We deploy it, we connect it to what you already run, we write down how it works.
- You
- Your access, and that is all.
- We
- We deploy it and write it down.
- 04
The handover
The code, the servers and the accounts go to your name. Walk away the next morning and everything keeps running without us.
- You
- You own it.
- We
- The repo and the accounts, in your name.
[09] After delivery
A breakdown at 3am? You get Loïs or Pascal.
No voicemail, no ticket, no tier-one reading a script. The two people who wrote your software are the ones who pick up.
The same number at 3am as at 3pm. It does not change after you sign.
- Who answers
- Loïs or Pascal. Nobody else.
- When
- 24 hours a day, weekends and holidays included.
- Where
- The same WhatsApp number as on day one.
- What we never do
- No chatbot. Ever.
[10] Who picks up
A father and a son.
No account manager. No junior learning on your budget. You talk to whoever writes the code.
Two of us. It keeps the meetings short.
How the two studios split
Loïs Bibehe
Co-founder · engineering
Pascal Bibehe
Co-founder · systems & operations
[11] The proof
We wrote encrypted video calls and messaging. Then we gave it away.
Calls, chat, file storage, community servers. Free under Apache-2.0, running on your own machine if you want, and nobody can take it back.
- Licence
- Apache-2.0. Commercial use included.
- Hosting
- Your machine, or ours. Your call.
- Accounts
- None required to run it.
- If we vanish
- It keeps working. A licence cannot be recalled.
$ curl -fsSL node.zippytal.com/install.sh | sh
✓ zippytal-node installed
$ zippytal enable meet chat drive
✓ 3 services healthyZippytal Meet
Encrypted video. On an SFU we wrote in Go.
meet.zippytal.com
Zippytal Chat
Encrypted messaging with files, voice and presence.
chat.zippytal.com
Zippytal Communitybeta
Federated community spaces, rooms and voice channels.
community.zippytal.com
Zippytal Drive
Encrypted file storage, distributed across your own nodes.
drive.zippytal.com
Zippytal Nodes
The peer-to-peer daemon the whole network runs on.
node.zippytal.com
[12] Start here
What should be running itself?
Tell us what eats the most time. We will tell you whether it is worth automating, and what it costs.
We reply on WhatsApp, usually within the hour.
- Firm price and firm date, agreed up front
- The repo and the accounts in your name
- A breakdown at 3am gets Loïs or Pascal
- No sales demo