Loading Donald Lena…
Custom software for contractors and service teams
Keep the whole job together.
A change is agreed in one place. A supplier receipt lands somewhere else. The office needs the whole story before the next invoice.
I build around those handoffs. First, we follow one job and check what your current tools can already do.

Choose the next move
Choose what to keep before choosing what to build.
The useful question is where the job record stops carrying enough context for the next person. The office, project lead and field team need to agree which record is current and who can change it.
- Keep
The existing tool carries the job and people can find the current record.
First improvement: Name the next action owner and agree a consistent job reference.
- Configure
The necessary field, permission, reminder or view may already exist.
First improvement: Test the supported settings on one example job before buying or building more.
- Connect
Two useful tools hold different parts of the record and a supported connection is available.
First improvement: Link one approved handoff, with record ownership, duplicate handling and a visible failure queue.
- Build
A repeated, verified need remains after those checks.
First improvement: Scope one missing step, with permissions, acceptance checks, handover and support agreed first.
These are options to evaluate with your team. An integration depends on the actual products, plans, permissions and supported interfaces.
Inspect the handoff
Follow one small handoff.
A change, a direct expense and completion evidence are separate records. This fictional example asks the office to review four chosen checks.
Change approval does not establish spending authority. A recorded expense does not establish what can be billed. Completed checks still need a person to review the contract, approvals and accounting treatment.
This illustrates records moving between people, without specifying how a trade should design or perform the work. It uses fictional records throughout and is independent of the retired MetroGlass app.
Explore the broader fictional job file Explore job costs and invoicesAdded access panel.
Separate records, linked to the same sample job. Try changing the four checks.
2 of 4 example checks complete
Review example blockers
Still to review: authority confirmed, completion recorded.
Changes stay in this page session and reset on reload. This example does not create or send an invoice, authorize a purchase or prove payment.
Before a build starts
Agree how the system will be owned and supported.
These questions belong in the written scope. A handover document or backup setting should be checked in use. Software delivery, integrations and ongoing support each need an agreed scope.
Accounts & access
Who controls the hosting, service accounts and repository? What access does each role receive?
Records & exit
Which tool owns each record? How does the business export its data, and what happens when the engagement ends?
Code & handover
Agree the rights to custom code, third-party components, documentation and team training.
Recovery
Who runs backups, what do they cover, and how will a restore be checked?
Running costs
Which subscriptions and usage charges does the business approve and pay?
Support
Agree maintenance, monitoring, failed-connection handling, support hours and response expectations.
Inspect the work and its limits
A past build you can inspect.
The MetroGlass Pro case documents an internal system I built around the glass-installation job sequence. The original database was deleted and the app is retired. Its preserved interface uses fictional records; it is historical implementation evidence.
Explore the MetroGlass caseThe Le Yard software case shows a system being built and rehearsed during pre-opening. It does not establish live restaurant results.
Explore Le Yard in developmentNeither example establishes savings or results for your business. A first release needs a specific acceptance check, followed by observation with the people doing the work.

Start with one job workflow
Which handoff should we follow?
Tell me the kind of work you do, the tools you use and the handoff you want to understand. A one-job operating review produces a workflow map, a prioritized handoff list and a brief for the first improvement.
We agree the review scope, fee and schedule before starting. Software delivery and support get a separate scope.
No customer files, private financial records or logins needed in this first note. Sending an inquiry does not book or start paid work.