About
We learned this software at the operations desk, not in a meeting room.
This product came out of sitting next to the people who build a flight school’s daily plan in a spreadsheet. That is where we learned which rule gets checked when, why a form is waiting, and which record an audit asks for.
How it started
The aim was not to build a product. The person preparing a flight school’s daily plan was writing the same information into three different places during the day: the plan file, the flight log, the student’s progress sheet. When the three did not agree, month-end lost a day.
The first version was only a planning screen. Then came “could we fill this form in here too”, then weight and balance, then licence dates. Every module came from a problem sitting on the desk that day, not from a product roadmap.
There are ten modules now, and they all work on the same principle: enter it once, and let it be correct everywhere.
How we work
Four principles
Rules at entry, not in reports
A report that finds a mistake afterwards is a good report; a form that prevents it is better. We put the checks at save time.
Screens follow the work
We build the menu around the shape of the day, not the shape of the database. Whoever is planning should finish the job without leaving the planning screen.
Fewer features, fully working
A half-working feature is worse than a missing one, because people rely on it. We ship a module only after it has run in a real school.
The data belongs to the customer
You can export all of it whenever you want. Keeping customers by keeping their data is not something we are willing to do.
Got a question?
Not everything has to be about the product. Write to us and we will answer.
No setup fee, no commitment. We usually get back to you the same week.