Our story

Why we built Pendira

A job should not live in six places. This is what we saw inside a field service company, and what we built instead.

The Pendira team2 min read

An engineer holds a network switch beside an open network cabinet

The first time we sat with a field service team, we counted the places one job lived. An email from the client. A row in a spreadsheet. A ticket in the client's portal. A message in a WhatsApp group. A missed call. And 14 photos on an engineer's phone. Six places, for one network switch in one store.

Nobody there was careless. The coordinators were sharp, the engineers were good, and the owner knew every client by name.

The work got done. It just did not get finished.

Done is not the same as finished

Finished means closed, billed and paid. Between done and finished, things fell through. A job was done on Thursday and nobody invoiced it. An engineer paid for parking and never got it back. A client asked for proof, and someone spent an hour scrolling through chats to find it.

Every month, someone checked by hand which jobs were done and which were billed. Every month, a few slipped through. Nobody could say how many.

The company in the middle

The more teams we spoke to, the clearer the pattern became. These companies sit in the middle. A client above them gives the work, often through a chain of other companies. Engineers below them do it, many of them freelance.

The tools on the market did not fit that middle. Marketplaces rent you strangers and take a cut. Field service suites are built for one company's own crew. Enterprise systems are sold to the company at the top of the chain. Nobody had built for the vendor who answers to both sides.

That vendor has a strange job. It has to show its client everything about the work, and nothing about the money. The client wants status and proof. The engineer wants clear instructions and to be paid right. The owner wants to know the margin, and to keep it private.

What we built

So we started with one rule: one job, one record. From the moment a client asks to the moment the engineer is paid, every job keeps its own story in one place.

  • Engineers get a text with a secure link and a code. No app to install, no password to forget.
  • Proof lands on the job as it happens: check-in, photos, checklist, signature.
  • Nothing closes until the costs are final, and closing writes what to bill and what to pay.
  • The client gets a read-only link with status and proof. Never prices.
  • Prices, rates and margins follow roles, and the server leaves out what someone may not see.

What we will not do

We will not become a marketplace. Your engineers are yours. We will not sell your data, to anyone. We will not move your money: we tell you exactly what to bill and pay, and your bank and accounting stay in charge. And when AI arrives in Pendira, it will propose and a person will decide.

Where we are

Pendira is built in the Netherlands and hosted in the EU. We are building it with our first customers, one week of real jobs at a time. If your jobs live in six places too, we would like to show you what one record feels like.

The Pendira team

Every job, from request to paid.

See Pendira with your own jobs in a 30 minute demo. Bring a messy week, and we will show you that week in one record.

EU based. GDPR compliant. We never sell your data.

A smiling engineer crouches with his laptop beside a server rack

Cookies, honestly

Necessary

Always on

The consent cookie itself. Nothing else.