Changelog

Released

July introduced Marni, an AI assistant built into the dashboard to answer questions and handle busywork, alongside a refreshed files and notes experience for keeping job documentation organized without extra tools.

Highlights

• Introduced Marni, an AI assistant that can answer questions and take action directly inside Ormi

• Gave Marni contextual awareness of jobs, customers, and schedules to keep answers relevant

• Rebuilt the files and notes experience for cleaner uploads, previews, and organization by job

• Improved conversation memory so Marni stays useful across a longer back and forth

• Refined the customer portal's authentication so returning customers move through it faster

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

May pushed payments further than collecting a balance, building out a dedicated customer portal with card, bank, and digital wallet options so customers could pay the way they already wanted to.

Highlights

• Launched a customer facing portal for viewing and paying invoices without an account or app

• Added Apple Pay, Google Pay, and ACH bank payment options alongside card payments

• Improved payment history views so office teams could see exactly how and when a customer paid

• Hardened the onboarding flow for contractors connecting their own payment accounts

• Refined deposit and partial payment handling across estimates and invoices

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 weeks after launch surfaced real usage patterns, so March focused on smoothing the calendar and customer records that teams were now relying on every day instead of just testing.

Highlights

• Refined the scheduling calendar based on real dispatcher usage patterns from the first launch weeks

• Improved customer record consistency so searching and selecting the right customer felt instant

• Tightened job list filtering and sorting for teams managing a growing volume of work

• Fixed edge cases in recurring and rescheduled appointments reported by early customers

• Polished dashboard loading states so the day's schedule felt immediate, not delayed

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

With mobile tools built and the core workflow proven, December was launch prep: fixing rough edges, tightening onboarding, and rehearsing the exact path a new contractor would walk through on day one.

Highlights

• Ran end to end testing across scheduling, jobs, invoicing, and payments ahead of launch

• Built the account and company onboarding flow new contractors would use to get started

• Fixed performance and reliability issues surfaced by internal dogfooding

• Polished empty states, error messages, and first run screens across the dashboard

• Finalized the per job pricing rollout that would define Ormi at launch

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

With dispatch and billing in place, October closed the loop between the office and the field, building the first notification and status update system so nobody had to call around just to find out what was happening on a job.

Highlights

• Built the first job status notification system connecting office, technician, and customer updates

• Added real time status changes so dispatchers could see delays and completions as they happened

• Refined the customer record view to surface active jobs and recent communication in one place

• Started laying groundwork for customer facing notifications ahead of the mobile rollout

• Reduced the manual phone check ins that had been filling the gaps between systems

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

August went deep on the logic behind the calendar, teaching the system how to reason about technician availability, travel time, and workload before the dispatch board could ship as a real daily tool.

Highlights

• Built technician availability and workload rules to support smarter scheduling suggestions

• Refined the assignment logic so dispatchers could reassign jobs without breaking the day's plan

• Added conflict detection for double booked technicians and overlapping appointments

• Improved calendar performance so a full day or week of jobs stayed fast to browse

• Prepared the groundwork that would become the dispatch board the following month

In development

With scheduling and customer workflows taking shape, July focused on making sure the money side held up under real use, from generating an invoice off a finished job to tracking whether it had actually been paid.

Highlights

• Refined invoice generation so billing stayed tied directly to completed job records

• Built out payment tracking states covering sent, partially paid, and fully collected invoices

• Started integrating card and bank payment collection into the same invoice workflow

• Improved customer billing history so past invoices and payments stayed easy to find

• Ran the first end to end tests of the job to invoice to payment pipeline

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

Before scheduling could feel effortless, the interface needed a foundation. May was spent building a shared design system and drafting the calendar and dispatch views that would carry the product through its next year of growth.

Highlights

• Built a shared component library so every future screen would look and behave consistently

• Drafted the first calendar and dispatch board layouts for reviewing daily technician workload

• Prototyped drag and drop scheduling interactions ahead of the June scheduling build out

• Refined navigation patterns so office staff could move between customers, jobs, and billing without losing context

• Started defining the mobile experience technicians would eventually use in the field

In development

April moved the plan from whiteboard to working software, standing up the first version of the office dashboard and proving that the customer, job, invoice, and payment relationships from March actually held up once real data started flowing through them.

Highlights

• Built the first working version of the office dashboard on top of the core data model

• Connected customers to jobs and jobs to invoices so the full lifecycle could be traced end to end

• Established the authentication and account structure every later feature would build on

• Started shaping the technician role separately from the office role, with its own permissions and views

• Ran the first internal walkthroughs with early contractor feedback to catch gaps before scheduling work began

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

With the mission set, February was about turning a field service platform idea into something concrete: a name, a pricing model, and the first sketches of how jobs, customers, and invoices would actually relate to each other on screen.

Highlights

• Landed on the Ormi name and the per-job pricing story that would carry through to launch

• Sketched the first entity relationships between customers, jobs, invoices, and payments

• Interviewed HVAC, plumbing, and electrical contractors to stress test early assumptions about daily workflow

• Drafted the initial information architecture for the office dashboard before any screens were built

• Set engineering conventions for the web app, API, and technician-facing surfaces that would carry the whole build

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