Run the week without the group chat.

How a job moves

Six steps, in the order they happen. Each one is a screen that exists.

1. 01

   The enquiry arrives as email

   Feldleiter reads your existing mailbox over IMAP. A client's email becomes a job in two panes: their whole thread on the left, the handover you are writing on the right, with a preview of what the crew will open. Attachments are sorted into what the crew reads, what the office keeps, and what nobody needs.

2. 02

   A job is a place

   Each job carries its own site address — “Apt 3A, rear building” is an address here, and no geocoder agrees. A dispatch inherits it, then keeps what it was sent with, so correcting the job later never rewrites a day the crew already worked.

3. 03

   You staff the week

   A grid of jobs by day. Click a cell, tick the people. The ones already on that job sort to the top; anyone on holiday sorts to the bottom with the reason, and stays tickable — you may know something the app does not. One site for three weeks is one action, and you can end it early or take a pause out of the middle.

4. 04

   The crew reports from the site

   Today, Week, Me — behind a bottom bar, built for a thumb in a glove. One card per site: the address, who else is there with a number to ring, what the office wants done, and the files it sent. Every write is queued offline and the app opens with no signal. Finished a day late? It can still be closed for the day it happened.

5. 05

   You check the work, the client accepts it

   Finished tasks wait on you, in one list across every job — approve, or send back with the reason, which files an Issue. When everything is approved the job is ready for the client: they open one link, with no account, see a report frozen for that round, and either accept it or point at the line that is wrong.

6. 06

   Nothing gets invoiced that nobody accepted

   Ready to invoice is reachable only from a client check, and only with that round's acceptance — or a written reason, filed under your name. At 18:00 in your own timezone, End of Day tells you what actually happened: the remarks, the acceptances, the crews that finished, and what is still waiting on you.

Price

Questions

Do my workers have to install anything?

No. The crew app opens in the phone's browser and can be added to the home screen, where it behaves like an app — full screen, works offline, sends notifications. There is nothing in the App Store or Play Store to find, and nothing to update.

What happens in a cellar with no signal?

The app opens anyway, from a cached copy, and every write — a task marked done, a photo, a note, “finished here” — is queued on the phone and sent when there is signal again. That is the normal path, not a fallback.

Which languages?

English, German, Serbian and Croatian. Every screen, in all four — the crew app, the office, the emails, the push notifications and the client's link. Each person sets their own; the client's link follows whoever sent it.

Does the client need an account?

Never. They open one link, look at the report for the check they were sent, and either accept it or raise an Issue against a line of it. You can email the link from your own mailbox, into the thread they already have with you.

Do you read my email?

Feldleiter connects to your mailbox with credentials you give it, encrypted at rest, and syncs the folders you point it at so a client's thread can sit on the job. You can also send from it, as your own address, so the client sees the company they wrote to. Disconnect it and the rest of the product still works.

Can I get my data out?

Your photos and files are yours and are stored as ordinary objects you can be given directly. The record of who did what and when is an append-only feed, exportable. There is no lock-in mechanism in the product.