Startups

Every customer, every hire, every number, on one system

Startups add a tool for every new problem until nobody knows which one is true. Start on one system that knows every customer, every asset and every hire, and put AI teammates on the work in between.

A mechanic tests an e-bike battery at the bench of a brick-walled Berlin workshop

Fast growth, held together by eleven logins

Most startups your size added a tool each time a problem showed up. It works until a rider’s battery dies at 7 a.m. and support, the workshop and the van each see a different part of it.

  1. A new tool for every new problemTickets in one app, deals in another, candidates in a third. Every new hire gets eleven logins and learns which one is true.
  2. The fleet lives in a spreadsheetWhich bike is where, who rides it and when it was last serviced sits in a sheet the workshop leads update when they remember.
  3. Support can’t see the workshopA rider asks when her bike will be back. Support asks the workshop in Slack, and the rider waits for both.
  4. The investor update takes a weekendEvery month someone pulls MRR, churn and fleet uptime out of five exports and into a deck by hand.
Spread across
  • Google Workspace Business Standard
  • Slack Pro
  • Zoom Workplace Pro
  • Otter Business
  • HubSpot Sales Hub Professional
  • Mailchimp Standard
  • Zendesk Suite Team
  • RingCentral Core
  • Calendly Teams
  • Asana Starter
  • Power BI Pro

$67,721 a year, at list price, for Pendel’s 11 subscriptions

Example companyPendel BikesBerlin, Germany

Pendel rents e-bikes to Berlin commuters by the month, service included, and runs employer plans for 60 companies.

Deniz Aksoy and Hanna Vogt started it in 2022 with forty bikes in a Kreuzberg courtyard. A Series A this spring paid for three workshops and 3,400 bikes, and took the company from 20 people to 48 in a year, on eleven subscriptions that don’t talk to each other.

48
people
3,400
bikes on the road
3
workshops
4
hires a month

Deniz Aksoy Co-founder and CEODesigns Pendel’s system with OpenLazarus in the film below.

Pendel Bikes is an invented example, not a client: a company like the ones we build for, made up to show how one would run on OpenLazarus. Its people, numbers and photographs are illustrative.

What Pendel runs on it

The modules carry Pendel’s names, not ours, and the AI teammates work on the same riders, bikes and candidates its people do.

Their modules
  • SupportEvery rider’s question, with the bike’s history beside it
  • Fleet3,400 bikes: who rides each, where it is and when it was serviced
  • PartsBatteries, motors and brake pads across three workshops
  • SubscriptionsEvery rider from sign-up to handover, and every return
  • EmployersThe 60 companies that pay for their staff’s bikes
  • HiringEvery open role and candidate, by stage
  • ReportsMRR, churn and uptime, ready for the investor update
  • PhoneThree lines for rider support and the workshops
Their AI teammates, on an example morning
  • Sam OkaforAIRider supportAnswered 214 rider messages overnight and had a dead battery swapped by 08:05
  • Mei TanakaAIService and dispatchBooked 38 service slots across three workshops and routed both vans
  • Amara DialloAIHiringScreened 96 applications for two mechanic roles and booked 7 interviews
  • Arjun MehtaAINumbers and investorsDrafted September’s investor update: MRR €268,900, up 6.1%

Companies like Pendel usually start with Sam, Amara and Arjun.

Illustrative estimate

What it could change in a year

An illustrative estimate for Pendel, worked from its example numbers: the subscriptions it would stop paying for, the hours its people would get back, and the bikes back on the road sooner.

$7,200
a year ahead: the eleven tools it would stop paying for cover Lazarus, its server, three phone lines and an engineer on call
2,100
hours a year it would give back to rider support, the workshops and the founders
94%
of service calls fixed within two days, up from 71% before every bike had a slot

Example figures for an invented company. The savings and hours are worked out from its example tools and plan at list prices; the third figure is an illustrative goal, not a measured result.

Start your company on a system you own

Tell OpenLazarus how your startup works today and where it is heading. You’ll see your system take shape in the conversation, with your names, your teammates and what it saves.

We’re 48 people. Isn’t this for bigger companies?

It is easier at your size. Every person you hire from now on joins one system, instead of you moving eleven tools’ worth of data when you are 150 people and the habits are set.

Do our app and our billing stay?

Yes. Your product team keeps building the rider app. Lazarus reads subscriptions and payments from your billing provider and the bikes’ data from your fleet platform, and writes back where it has to.

Where does our riders’ data live?

On your own server, which can run in the EU, and you own the data. Riders’ details sit in one place instead of eleven, which makes access and deletion requests simpler to answer.

Who decides what the AI is allowed to do?

You do, per teammate: what they handle on their own, and what they ask first, such as a goodwill credit over €50 or retiring a bike. Every action is logged where your people can see it.

How long does it take to set up?

The design takes one conversation with OpenLazarus, like the one in the film. Our engineers then connect your billing, phone lines and fleet data and move what you have, usually within a few weeks for a company Pendel’s size.