Loading Donald Lena…
Custom business software · New York
Build the software your business wishes already existed.
Donald designs and builds custom operating software for contractors, local service companies and hospitality teams. Start with the work that feels disconnected, then connect the tools already in use or build a clearer system around the team.
Start with the operation
The product brief comes from the real sequence: who does what, what information they need, where context gets lost, and which decisions must stay human. Existing texts, spreadsheets, forms, and workarounds are treated as evidence.
One connected workflow
Customers, jobs, reservations, staff, inventory, invoices, payments, documents, tasks, and reporting can live in one role-aware system when the business needs them to. The scope is based on the constraint, not a preset package.
Built for the people using it
Interfaces are mobile-first where work happens on the floor or in the field. Access, terminology, status, actions, and training are designed around each role so the tool is useful during a real shift or workday.
Automation with control
AI and automation remove clerical work, surface the next action, and help interpret records. Quotes, purchases, payroll, guest data, payments, and other consequential actions keep clear permission, evidence, approval, and recovery boundaries.
Published proof
Evidence before theory.
Useful questions.
What kind of custom software does Donald build?
Examples include restaurant operating systems, reservation and guest tools, job and field-service apps, estimate and invoice workflows, payment collection, scheduling, purchasing, inventory, internal dashboards, client portals, reporting, and AI-assisted operations.
What can a useful first release include?
The first release is scoped around one working sequence. For a trade business, that might connect inquiry, estimate, deposit, measurement, scheduling, field notes, invoice, payment, and closeout. For a restaurant, it might connect reservations, guest context, staff scheduling, purchasing, service tasks, closeout, and reporting. The exact sequence comes from the operation, not a preset feature list.
Who is this for?
The best fit is a founder-led or operating team with a real workflow problem: too many spreadsheets, messages, duplicate entries, missed follow-ups, disconnected tools, or important context living in one person’s head.
Does Donald use off-the-shelf software too?
Yes, when it solves the problem cleanly. Custom software is most valuable when the workflow is specific, several tools need to connect, or the operating advantage comes from handling the work in a way generic software does not.
How is a project priced?
There is no public fixed package. Donald first reviews the current operation, users, data, integrations, risk, and smallest useful release, then proposes a concrete scope.
What should I bring to the first review?
Bring the workflow that feels stuck, the people involved, the tools already in use, the information that gets lost or entered twice, and the decision or handoff that needs to become clearer. Private customer records, passwords, and financial files are not needed for the initial review.
Start with the current constraint
Bring the business, the evidence, and the part that feels stuck.
Donald reviews the public customer path, the operating handoff behind it, and the proof already available. Scope is set after review; there is no public fixed-price package.