Prepared by Jean-Luc Cooper
AIO Operations Platform
Clear control of your equipment, teams and jobs.
A platform built around how AIO works: knowing what is available, what has gone out, who has it and what still needs attention.
Information gathering, platform development, testing, pilot, training and handover support are included in this implementation.
See the last recorded location and assignment of equipment.
- Delivered through
- Equipment records, team assignments and location transfers.
- AIO's part
- Record movements when they happen.
What's included
What Jean-Luc will build for AIO
Overview
See this week's work and the items needing attention.
Included in the build
- This week's actual jobs visible immediately
- Assigned teams and vehicles
- Job progress and outstanding equipment
- Missing, damaged and unresolved items
- Links to the relevant records
Why this matters
Management can understand the current position without contacting several people.
Who uses it
- Management
- There is no “latest activity” feed on the main screen. It shows the work and the issues, not a stream of updates.
Access
Full control for management. Clear actions for the team.
Management / administrator
Full access across the platform — not a read-only dashboard.
Can
- View all jobs, equipment, assignments, locations and reports
- Create and edit operational records
- Perform the operational actions available to other roles
- Manage people, teams, vehicles and permissions
- Maintain kit definitions
- Review and authorise corrections or final issue outcomes
Roles and permissions are confirmed from AIO's existing responsibilities during information gathering.
The finished web app works through supported phone, tablet and computer browsers. Staff do not need to use the Lovable builder.
Build process
From AIO's information to a tested working platform.
Stage 1 · Gather & confirm
Information coming in: AIO's current operation and records.
What Jean-Luc does
- Provides straightforward information templates
- Walks through the current job-to-return process
- Gathers and organises supplied information
- Identifies missing details and clarifies them with AIO
- Confirms the required features and access rules
What AIO supplies
- Equipment names, descriptions, quantities and condition
- Existing categories, accessories and approved kit contents
- People's names and current responsibilities
- Team membership and team leads
- Vehicle names or numbers and assignments
- Warehouses, containers and storage locations
- Who may view, edit, approve and correct records
- Examples of job instructions
- Important exceptions and practical device/connectivity requirements
AIO confirms the accuracy of the physical inventory and operating information. Actual catalogue photographs are optional.
What moves to the next stage
Confirmed information, an agreed workflow and a clear build scope.
6–8 weeks + 30 days support
Indicative implementation: 6–8 weeks, followed by 30 days of handover support. The detailed schedule is confirmed after information gathering. Timing depends on complete information, feedback and staff availability.
How we will know it is ready
- Equipment quantities reconcile across issue, transfer and return.
- Missing and damaged items remain visible.
- Partial returns do not incorrectly close outstanding balances.
- Field updates reach the authorised users.
- Role permissions work as agreed.
- The nominated staff can complete the core tasks.
- No unresolved fault prevents use of a core agreed workflow.
Training
Support through the handover.
01
Live training
Two live sessions, up to 90 minutes each
02
Recorded guidance
Recorded walkthroughs and short visual guides
03
Handover
Administrator access and project handover
04
30-day support
Remote support plus two scheduled 30-minute follow-ups
- Training covers Andre / the nominated administrator, and the warehouse / selected team leads.
- Sessions are coordinated around pilot readiness and handover.
- Up to two additional hours of usage guidance are included.
- Faults in the agreed delivered features are corrected during the support period.
- AIO nominates one main support contact.
- Initial response target: two business days. Response time is not a guaranteed resolution time.
- New development, third-party outages and 24-hour support are outside this package.
Additional Lovable orientation
One 45-minute session showing Andre how to begin a separate interactive proposal or presentation-style page.
This is introductory guidance, not the delivery of additional projects. Those exercises use a separate project.
Scope
Who provides what.
AIO
Provides the operating information
- Accurate starting inventory and equipment descriptions
- Current people, roles, teams and vehicles
- Locations and approved kit contents
- Job-instruction examples
- Decisions about permissions and responsibilities
- Suitable devices and internet
- Feedback, training attendance and pilot participation
Jean-Luc
Builds and implements the platform
- Information templates and organisation
- Workflow and access design
- Platform development
- Configuration and import of AIO's supplied information
- Representative visuals where useful
- Testing and debugging
- Review sessions and agreed refinements
- Pilot support
- Training and handover support
Current operation
The implementation covers AIO's current inventory, people, teams, vehicles, locations and approved kits identified during information gathering.
Ordinary records can be added later through the completed features.
Corrections needed to make an agreed feature work are included. New features, integrations or changes to an approved workflow are discussed separately, with any additional cost and timing agreed before work begins.
- Procurement
- Accounting, invoicing and payroll
- Physical stocktaking and on-site photography
- Historical record reconstruction and ongoing data-entry services
- Automatic WhatsApp integration
- Native mobile apps
- Full offline synchronisation
- GPS tracking and route planning
- Hardware
- New modules or integrations outside the agreed scope
The initial field workflow requires internet and clearly shows whether a submission succeeded.
The engagement includes one consolidated working-build review and one consolidated pilot-feedback round. Fault correction is not counted as a new feature.
Investment
One implementation. A clear scope.
One-time implementation fee
US$3,500
Covers information gathering, the platform build, testing, review, pilot, training and the defined handover support.
What the fee includes — select a part
Templates, process walkthrough and organisation of AIO's supplied information into a confirmed scope.
Separate · paid to Lovable
from US$25 / month
Lovable Pro currently starts at US$25 per month, paid directly to Lovable.
Actual running costs depend on usage. Hosting resources, storage and AI features can consume credits. US$25 is the starting subscription price, not a guaranteed total monthly cost.
Additional credits, a domain or other agreed third-party services are separate. Usage will be reviewed during the pilot.
Jean-Luc's own development-tool usage is included in the implementation fee.
Lovable pricingQuestions
Common questions.
Will the team need to type a lot?
Routine actions use saved information, familiar names, visual references, buttons and quantity controls. Photos and short voice notes can add context.
Are real equipment photographs required?
No. Representative illustrations can support the catalogue. Accurate descriptions and identifiers are supplied by AIO. Actual photos can be added later or used in issue reports.
Can management do everything?
Management has full access to the platform's operational and administrative functions. Other roles receive the permissions agreed with Andre.
Can team leads report issues from the field?
Yes, through their permitted mobile web view when connected.
Can we still use WhatsApp?
Yes. Job sheets can be downloaded and shared, and instructions can be pasted or uploaded for review. Automatic WhatsApp integration is not included.
What if the AI makes a mistake?
AI prepares drafts and explains recorded information. A person checks the draft and confirms physical movements. Manual actions remain available.
Are you creating our teams or inventory?
No. AIO supplies its actual people, team structure, equipment and quantities. Jean-Luc organises and configures that information within the platform.
Can we add equipment and staff later?
Yes, through the completed administration features. New functionality is a separate discussion.
What happens after support ends?
AIO retains the handed-over platform and administrator access. Further support, maintenance or development can be agreed separately.
A clear build. A tested process. A supported handover.
The next step is to confirm the scope, nominate AIO's main contact and gather the information needed to begin.