Business applications
Business tools that fit the way you work.
Do you carry out site visits, produce reports or follow up with clients regularly? Lezo turns a process scattered across files, emails and tools into a single application, about five times cheaper to build than before thanks to AI.
01Situations
Do any of these sound familiar?
These needs are common in specialised service companies. During scoping, we check together whether they justify a custom tool.
Information entered twice
Readings, photos and notes are taken on site, then typed again at the office.
Reports that take too long to compile
Every report means gathering files, copying tables and checking the same information again.
Tracking that is hard to share
Cases, interventions and action plans live in spreadsheets and inboxes; nobody has the full picture.
Clients asking where their case stands
Your clients want to see their documents, follow progress or send information without going through email.
02Cost
Custom software is no longer reserved for big budgets
Until recently, a custom business tool cost around €100,000, then €20,000 to €30,000 a year in maintenance and improvements. With supervised, AI-assisted development, Lezo delivers the same quality for about a fifth of that.
- Build
- Classic development: €100,000With Lezo: €20,000
- Maintenance and improvements, per year
- Classic development: €25,000With Lezo: €5,000
Indicative orders of magnitude: the actual estimate depends on your scope.
How we use AI
- 01
AI writes, a developer decides
Architecture, technical choices and the approval of every change stay in the hands of an experienced developer.
- 02
Every change is checked
Code review, automated tests and regular demos: AI speeds up delivery, with no shortcuts on quality.
- 03
Standard code that you own
Widely used technologies, readable and documented code: another team can take it over at any time.
03Subscription or software
Your own software, for the price of a subscription
A SaaS subscription is paid every month, per user, for as long as you use it. With development costs divided by five, a tool built around your process costs the same over five years, then less every year after.
After 5 years, a SaaS subscription and your software have each cost about €45,000. After that, the subscription costs €9,000 per year, your software €5,000.
- SaaS subscription15 users at €50 per month
- Your software with Lezo€20,000 to build, then €5,000 per year
A SaaS subscription
- Features designed for everyone, worked around for your case.
- A per-user price that grows with your team.
- A cost that never stops.
- Data and improvements that depend on the vendor.
Your software
- Built around your actual process.
- A cost that does not depend on the number of users.
- A tool you own, with its code and documentation.
- Improvements decided by your priorities.
Indicative assumption. Off-the-shelf software is sometimes the right answer: scoping compares both options.
04Example solutions
What we can build
These are only examples. Your solution starts from your actual process; sometimes adapting an existing tool is enough.
- Example use case
Mobile field data collection
Forms, photos and readings captured on site and available at the office without re-entry.
- Example use case
Document generation
Reports, minutes and summaries generated from collected data, in the format your clients expect.
- Example use case
Case and action tracking
Assignment, deadlines, statuses and history shared by the whole team.
- Example use case
Client portal
A space where your clients see their documents, follow progress and send you information.
- Example use case
Connections to your tools
Data exchange with your existing software: accounting, CRM, file storage or messaging.
05Two use cases
Equip your team or extend your service
A company may need one, the other, or both. We separate them from the start, because their value isn’t measured the same way.
Equip internal operations
- Intended benefit
- Reduce manual handling and help information flow between people.
- Checked during scoping
- Process, frequency, time lost, users and integrations.
Extend a service to your clients
- Intended benefit
- Offer tracking, access to information or a new service to your clients.
- Checked during scoping
- Real client demand, adoption, operations and any business model.
06Process
From today’s process to a tool in daily use
A limited first version, tested with your users, then new features decided with your business contact.
01
Understand your process
Interviews with the people involved, review of the files and tools in use, identification of friction points.
02
Compare the options
Off-the-shelf tool, integration, adaptation or custom development: we recommend the best fit, even when it is not custom software.
03
Define a first version
One priority use case, shared success criteria and mockups to validate how it works.
04
Build and test
Development in stages, regular demos and testing with the people who will use it.
05
Roll out
Go-live, migration of existing data when needed and support for the first users.
06
Support and evolve
Hosting, maintenance and improvements, as agreed in the contract.
Deliverables
What each proposal specifies
- A scope and shared success criteria.
- User flows or mockups to validate how it works.
- An application or integration tested with your users.
- The documentation needed to operate and take over the tool.
- Access, delivery and support terms.
Getting started
What makes a good project
You do not need a technical team. These conditions help launch a useful first version:
- A real process you can show, and whose frequency you know.
- A business contact who can make decisions.
- Users ready to test the workflows.
- A decision-maker who backs the project and plans for the tool’s life after delivery.
07After delivery
Business software needs care after launch
Once in service, your tool is part of your team’s daily work. From the proposal onwards, we plan how it will be hosted, maintained and improved.
Hosting and operations
Deployment, backups and monitoring, in the environment chosen together.
Maintenance
Fixes, security and dependency updates, monitoring that everything works.
New features
Improvements prioritised with your business contact, based on user feedback.
Documentation and takeover
Choices and operations are documented, so the tool can be taken over if your organisation changes.
08Budget
How the budget is built
Budget and schedule depend on what exists, the use cases and the chosen scope. As a rough guide, allow about €20,000 for a first version and about €5,000 a year to keep it running. The proposal separates three parts:
01
Initial build
Scoping, first version, testing and go-live.
02
Running costs
Hosting, maintenance and any third-party services, planned from the start.
03
New features
Improvements decided as the tool is used, quoted separately.
You can contact us without a set budget: the first conversation also helps size the investment.
You bring your knowledge of the business. Lezo handles the technical choices and the build, with checkpoints defined together.
Proof
A web and mobile product we operate
Questovery combines a web editor, a mobile app and experience tracking. Lezo designed it, builds it and runs it every day: the same standards apply to our clients’ tools.
Read the Questovery case studyMore references will be published once the clients involved agree.
FAQ
Your questions about business applications
Why not use off-the-shelf software?
Sometimes that is the right answer. Scoping compares available solutions, integrating existing tools and custom development. With AI-assisted development, custom software costs about five times less than before: over a few years, it often matches the price of a subscription. We recommend it when your process justifies it.
What happens to our existing files and data?
Their migration is studied during scoping: formats, volume, quality and history to keep. The proposal states what is migrated and how.
How do we make sure the team will use the tool?
Users are involved from scoping and test the flows before go-live. The first version focuses on one use case, so it gets adopted before it grows.
Who maintains the application after delivery?
Lezo can take care of it: hosting, maintenance and improvements are set out in the contract. The documentation we deliver also lets another team take over the application.
How is the budget set?
From the scope of the first version, the integrations needed and the level of support you want. The proposal separates the build, running costs and new features.
How does your team work today?
Where do you lose time? Who will use the tool? A few lines are enough to prepare the conversation.