Changelog

Released

We expanded the system beyond first-visit job completion so office teams could manage return work, warranties, and longer customer relationships without falling back to spreadsheets or manual callback lists.

Highlights

• Expanded follow-up scheduling so teams can queue return visits, reschedules, and unresolved work directly from the original job

• Added stronger warranty workflows so completed service and install work remains connected to future covered visits

• Improved job history with attachments, notes, status activity, and supporting records to create a clearer long-term service timeline

• Refined assignment and rescheduling flows so dispatchers can react faster when a technician route or job plan changes mid-day

• Continued tightening the full lifecycle from scheduled to in-progress, completed, invoiced, paid, and revisited when needed

Released

After launch, we focused on reducing back-and-forth between the office, technicians, and customers by tightening the communication layer around active jobs and daily field updates.

Highlights

• Improved technician status updates so office teams can see progress, arrival changes, and completion signals more clearly during the day

• Expanded customer-facing notification flows around dispatch, arrivals, job progress, and follow-up communication

• Refined mobile-friendly notes, photos, and signatures so field documentation is easier to capture while the work is happening

• Improved customer records so job history, invoice history, communication context, and service details stay in one place

• Made daily handoffs between dispatchers, technicians, and customers faster with fewer manual check-ins

Released

The first post-launch cycle focused on helping owners and office managers see more of the business in one place, from completed work and invoice flow to payment collection and operational reporting.

Highlights

• Expanded reporting around job volume, completion rates, revenue trends, and day-to-day operational visibility

• Improved invoice creation directly from completed jobs so billing stays tied to the actual work performed

• Refined payment collection, balance tracking, and reconciliation workflows around customer billing

• Added clearer visibility into sent, unpaid, partially paid, and completed billing activity for office teams

• Polished dashboards and reporting surfaces so teams can spot performance and collection issues faster

Released

Ormi officially launched with the core workflows field service businesses need to run the full job cycle, from the first customer call and scheduling decision through field completion, invoicing, and payment collection.

Highlights

• Released the core dispatch and scheduling workflow for office teams managing technicians, time slots, and changing priorities

• Launched customer management with centralized contacts, locations, service history, and job context

• Shipped job tracking from creation through scheduling, field updates, completion, invoicing, and payment

• Released technician mobile workflows for job updates, notes, photos, signatures, and on-site visibility into customer details

• Introduced Ormi's simple per-job pricing model instead of traditional per-seat monthly subscription pricing

In development

As launch approached, we focused heavily on the technician experience so field teams could work from their phones in real conditions instead of depending on office staff to close every loop for them.

Highlights

• Built mobile workflows for job details, status updates, customer context, and technician field notes

• Added photo capture and attachment support so crews can document work without separate tools or post-job upload steps

• Developed digital signature capture tied directly to the job record for cleaner closeout workflows

• Improved technician-facing completion steps to reduce missed paperwork, missing notes, and end-of-day office cleanup

• Tested faster mobile navigation for crews moving between multiple jobs, addresses, and service calls in one day

In development

This phase connected the office-side workflow so dispatchers and office staff could manage the daily operation from one place instead of bouncing between calls, spreadsheets, and disconnected billing tools.

Highlights

• Built the dispatch and job management foundation around calendar scheduling, technician assignment, and daily workload visibility

• Expanded customer records so office teams could track contacts, service locations, history, notes, and repeat work in one view

• Developed invoice creation from completed work instead of forcing separate manual billing steps after the job

• Connected job status changes back into the office workflow so teams could see what was scheduled, active, delayed, or completed

• Improved the day-to-day flow for creating jobs, editing details, reassigning work, and closing out service calls

In development

By mid-2025, the platform had moved well beyond planning and into practical service workflows for scheduling work, organizing customer history, generating invoices, and collecting payment in the same operating flow.

Highlights

• Developed the scheduling and calendar workflows that became the foundation of the dispatch experience

• Built customer-to-job relationships so office teams could see work history, locations, notes, and open tasks in context

• Started integrating invoices and payments into the same workflow instead of treating billing as a separate system

• Improved dashboard patterns around jobs, customers, scheduling, and billing so navigation felt operational instead of fragmented

• Shaped the core contractor workflow around HVAC, plumbing, electrical, and remodeling use cases with different visit and billing patterns

In development

We spent the early build phase mapping the real-world flow from first customer contact to closed-out job so the product structure would match how service businesses actually operate day to day.

Highlights

• Defined the core job lifecycle covering intake, scheduling, dispatch, field work, completion, invoicing, and payment

• Started building the first versions of the office dashboard and shared operational data model

• Outlined the technician and office handoff points that shape scheduling, field updates, and customer communication

• Established the customer, job, invoice, and payment relationships that would support the rest of the platform

• Focused the roadmap on simple field service workflows instead of bloated enterprise admin complexity

In development

Work on Ormi began with a clear goal: build a field service platform that handles scheduling, jobs, customers, invoices, and payments without the complexity, seat-based pricing, and operational sprawl of traditional systems.

Highlights

• Started product planning around the full field service workflow from office staff to technician to customer

• Set the initial direction around jobs, scheduling, dispatch, customer management, invoicing, and payments

• Established the first platform architecture for the web app, API, and technician-facing workflows

• Defined Ormi's pricing philosophy around completed jobs instead of recurring per-user subscriptions

• Began turning contractor workflow pain points into the first major product milestones and launch priorities