Custom operations platform + AI for trades

Less Job Chasing

A platform built around your office, crews and customers. Current scope, clear owners and selected AI tasks—all connected to the job.

Map your workflow See how it works

For trades teams with a real office-to-field handoff problem.

One job ID, shared context

Keep scope, people and evidence connected.

Illustrative job recordOne shared job ID

Every handoff. Same record.

Approved scope → crew handoff → completion evidence

ScopeCurrent approved version

Next actionNamed owner

ChangesApproval + history

CompletionPhotos + sign-off

OfficeCrewClientBilling

Workflow concept, not a live product screenshot. Your build uses the modules and checks you agree.

Illustrative job flow

A clear path through every job.

We adapt the stages, owners and readiness checks to your operation.

01
Capture the request
Office / sales
Create the job record; attach customer details and the source conversation.
02
Agree the scope
Estimator + customer
Record work, exclusions, materials and access; keep the accepted version.
03
Check readiness
Coordinator
Check required information, materials, crew, date and unresolved questions.
04
Hand over to the crew
Coordinator + crew lead
The crew receives the current job pack and confirms the handoff.
05
Capture work from site
Field team
Add photos, notes, voice updates, time and agreed completion checks.
06
Approve changes
Named approver + customer
Record scope, price and schedule effects. Approve before changed work.
07
Confirm completion
Crew lead + office
Collect agreed evidence and sign-off; assign unresolved items before billing.
08
Pass the record to billing
Office / finance
Prepare invoice details against the job and approved changes.

When something is missing.

Flag the gap → assign an owner → resolve it or record an approved exception → continue.

Critical handoffs use agreed readiness checks. Client approvals, signatures and billing connections are included where agreed in scope.

Choose the screens that solve the gap

Built around how you work.

Job workspace

Current scope, instructions, files, status, responsibilities and version history.

Mobile field workspace

Photo, note, voice and signature capture with job-linked checklists.

Schedule + crew planner

Assign work against status, availability, readiness and agreed travel rules.

Change + approval workspace

Connect each change to scope, impact, approver and customer response.

Client portal

Selected updates, photos, approvals and documents; internal records stay private.

Costs + billing workspace

Agreed cost inputs, purchase orders, invoice drafts and scheduled reminders.

Lead + communication workspace

Capture enquiries and route call or message summaries when in scope.

Reporting + job history

Progress, exceptions, costs and evidence exports from the data captured.

A tailored-build menu, not an all-inclusive bundle. Your proposal confirms selected modules, limits and acceptance criteria.

The AI layer

Prepare the work. Keep people in control.

The platform keeps the record. AI helps capture, check and prepare it.

Scope extraction

Prepare structured details from approved quotes, emails and PDFs.

ControlKeep the source link; people review critical facts.

Voice + photo capture

Prepare notes, actions and photo tags from field updates.

ControlThe user confirms before the record changes.

Missing-information checks

Flag missing required fields or evidence and draft a request.

ControlAgreed rules; a named person resolves gaps.

Change-order drafts

Prepare a summary and quote/PDF using approved rates.

ControlPeople approve scope, price and release.

Enquiry triage

Summarize calls/messages and suggest a category or dispatcher.

ControlAgreed routing, escalation and uncertain-case handling.

Routine communication

Draft current job updates and payment reminders.

ControlApproved templates, recipients and send triggers.

Evidence + job search

Organize files, prepare bundles and answer job-history questions.

ControlRestricted access; answers link to source records.

Risk flags — advanced option

Flag overdue approvals, incomplete work or unusual cost movement.

ControlRules first. Predictive scoring needs suitable data and validation.

Fixed rules can handle scheduled reminders and required-field checks. Every automation has agreed inputs, outputs, triggers, permissions, review steps and a fallback owner.

Connection feasibility comes first

Use the tools you already have.

Accounting + payments

QuickBooks, Xero and existing payment or payroll tools.

Field + documents

Fieldwire, Raken, Bluebeam and existing Autodesk or drawing workflows.

Messages + calls

Email, SMS and call logs; approved WhatsApp or file imports where permitted.

Materials + suppliers

Approved catalogs, prices, stock or purchase-order data where available.

Your bespoke stack

Available APIs, webhooks and connectors; n8n or Zapier where suitable.

Dependable sync

Agree field ownership, sync direction, timing, visible failure status and the person who resolves it.

Examples for review, not confirmed connections or partnerships. Access, API support, licensing, data quality and regional availability determine what can be included.

Practical controls, agreed up front

Clear access. Recorded history.

Role-based access

Agree who can see each job, document and action, including clients and subcontractors.

Security + recovery

Scope client-data separation, encryption, backup and recovery requirements.

AI data use

Agree providers, permitted information, retention and access before configuration.

Ownership + export

Agree event history, evidence exports, data/code ownership and handover terms.

Offline drafts, sync status and conflict handling are scoped and tested if required. Evidence exports support record keeping; they do not certify compliance.

How we build with you

From workflow to working platform.

01
Diagnose
Review recent jobs, tools and costly handoffs. Choose the first priority.
02
Scope
Agree screens, roles, integrations, AI tasks, inputs and acceptance checks.
03
Build
Build the agreed workflow and connections. Demonstrate labelled examples.
04
Check
Test representative jobs, permissions, approvals, gaps and failures.
05
Roll out
Prepare data, train users and name the rollout owner.
06
Measure
Compare the pilot with its baseline, adoption and agreed measures.

Track missing details, clarification time, avoidable repeat visits, approvals, invoice readiness and actual adoption against your own baseline. Results depend on the agreed workflow, reliable inputs and team adoption.

Fit before a build

Solve a confirmed workflow gap.

Worth a conversation

Several roles or crews pass job information.
A recent breakdown has a cost you care about.
Existing tools still leave an identifiable gap.
An owner can provide data, decide and support adoption.

When not to build

Your current workflow works well.
A simple configuration in an existing tool solves it.
There is no costly handoff problem.
No accountable owner or reliable data access.

Starting focus: US and UK HVAC and plumbing teams. Workflow complexity matters more than a headcount cutoff.

Current price and proposal

Know what the build includes.

Current base price

Custom build + servers.

One-time setup / custom build€5,000

Servers€100/month

Scope, AI usage, external tools, maintenance, support and future changes follow your agreed proposal. Before tax or agreed extras.

Review the build scope

Transparent base-cost calculator

Plan the base.

Months of servers 12

Setup + selected server period€6,200

€5,000 + (€100 × months). Base-cost planning only, not an ROI forecast or a final quote.

Your proposal confirms milestones, payment schedule, acceptance, support, ongoing costs, changes, ownership, exports and handover. No fixed public completion deadline is promised.

Questions before a fit review

Check the real fit.

What is a custom operations platform for trades?

It is software built around the way your office and field crews pass work between people. Launchzy maps the workflow, builds the agreed screens and shared job record, and adds selected AI tasks. Modules, integrations, limits and acceptance checks are written into your proposal.

Who is this best for?

HVAC, plumbing and other trades businesses with several people or crews, regular office-to-field handoffs and a recent costly workflow problem. A workflow owner must be able to provide inputs, make decisions and support adoption. Headcount alone does not establish fit.

What does the platform cost?

The current base price is €5,000 one-time setup/custom build plus €100/month for servers. Twelve months of servers plus setup is €6,200 before tax or agreed extras. Your proposal confirms AI usage, external tools, maintenance, support, future changes and commercial terms.

Is every module included?

No. The modules on this page are a menu for a tailored build. Your proposal identifies selected modules, workflows, integrations, limits and acceptance criteria. We diagnose the confirmed gap before agreeing the build.

Can it connect to our existing tools?

We review available APIs, permissions, licenses and data quality first. Accounting, field tools, messages and supplier systems are integration candidates, not confirmed connections. Each included sync needs a source of truth, direction, timing, visible failure status and fallback owner.

Does AI approve changes or send messages by itself?

People approve critical scope, pricing and release decisions. For every automation, we agree the input, output, trigger, permissions, review step and fallback owner. Routine reminders can use fixed rules; AI is used where interpretation helps.

Can crews work offline?

If offline working is required, we scope saved drafts, sync status and conflict handling, then test weak-signal conditions. Offline behavior is not included automatically.

What if our existing software can solve the problem?

A simple configuration in your current tool may be the better fit. We use a recent job and your existing tools to establish the gap before recommending a custom build.

How long does a build take?

Delivery milestones are agreed after workflow discovery and scope review. There is no fixed public completion promise: timing depends on the selected modules, integrations, available data and acceptance checks.

Will it guarantee savings or compliance?

No. Outcomes depend on the agreed design, reliable inputs and team adoption. We compare the pilot with a baseline and agreed measures. Evidence exports help record keeping; they do not certify compliance. Security and AI data-use requirements are agreed before configuration.

The first conversation

Bring one broken handoff.

Bring a recent job, your current tools and the workflow owner. We’ll map the gap and assess whether a custom build makes sense.

Map your workflow See every solution