Skip to content
Oleera
Request access
Product Operations Pricing Resources FAQ About
Sign in

The product

One record of a customer. One record of the work.

Oleera is not a suite of separate products behind one login. Everything below reads and writes the same records, which is why the reporting at the end of this page is possible at all.

Customers

Who they are, and where they came from

Contacts

The customer record, with every call, text, email, form submission and note against it in one timeline. Phone numbers are normalised on the way in, so a text from a number saved three different ways still lands on the right person.

Properties

The address is its own record, not a field on a person. It outlives whoever was paying at the time, which is what you want when a house sells and the new owner calls about the same water heater.

Equipment history

What is installed at an address, when it went in and what has been done to it. The reason a technician arrives already knowing what they are looking at.

Pipeline

Deals through stages with value and age. The lead source is stamped on at creation and never recalculated, so a report six months later still says where the work came from.

Tasks and inbox

One stream of everything that came in, filterable by kind, plus the tasks that came out of it. Both are shared, so work does not live in one person's head.

Import

CSV import for contacts, properties, products and deals, with a preview of exactly what will happen before it happens. Addresses on a contact row become properties automatically.

Money

Quote it, bill it, collect it

Proposals and estimates

Line items from your price book, your terms, your branding. The customer signs on their phone with a finger and the signature is stored with the document.

Invoices

Raised from a proposal or from scratch, sent by email, paid online. Invoices attach to jobs many-to-many, because one invoice covering three visits is normal and most systems cannot represent it.

Payments

Card and ACH through your own Stripe account. You are the merchant of record, the money settles to your bank, and ACH is only marked paid once the funds actually clear rather than when the customer clicks pay.

Price book

Products and services with both a cost and a price, which is what makes margin per job a real number instead of an estimate.

Recurring plans

Maintenance agreements that raise their own invoices on schedule.

Revenue reporting

Revenue by lead source, recognised on the close date rather than the date a record was created. Margin per job. The report the incumbents cannot produce.

Getting work

Fill the calendar, and know what filled it

Email campaigns

Sent from a domain you verify, so your sending reputation is yours. Real metrics including why a message was skipped, which is the number that tells you something is wrong with your list.

Lead capture forms

Hosted forms that write straight into contacts with the source attached, plus a webhook if you would rather post from a site you already have.

Automations

Triggered sequences that read as English sentences rather than a diagram. When a form is submitted, wait ten minutes, then create a task. You can read what an automation does without opening a builder.

Booking pages

A public link that reads your real availability, respects your working hours, and creates the visit. Not a calendar widget bolted on the side.

Text messaging

Two way SMS on the contact record, with a real carrier registration check so messages do not silently fail the way they do when a number was never registered.

Client hub

A link a customer can open to see their documents and history without an account, a password, or a phone call to your office.

Ask Oleera

An assistant that reads everything and sends nothing

Ask it anything about your business in plain English. Which customers have not been back in a year. What the Google campaign actually earned last quarter. Who is unassigned on Thursday. It reads the same records you do, so the answer is the answer rather than a guess.

It also does the work. Draft the follow-ups for every overdue invoice, write the estimate from these notes, tag everybody who bought a softener in 2024. Each one arrives as a proposed change you approve or reject, with the reasoning and the records it read attached.

Standing instructions run on a schedule. Every Monday morning, a summary of the week ahead and what needs a decision. It will be waiting for you. It will not have been sent to anybody.

How a change happens

  1. 1 You ask In plain English, the way you would ask an employee.
  2. 2 It reads Your records, scoped to your business and nobody else's.
  3. 3 It proposes A plain-English diff of exactly what would change, and why.
  4. 4 You approve Or edit it first, or reject it. Nothing has happened yet.
  5. 5 Code executes Ordinary deterministic code applies the approved change. Not the model.

Not yet

What Oleera does not do

This list is here because a page that only lists strengths is not information. Everything below is either being built or deliberately out of scope, and none of it is on this site pretending otherwise.

  • Review generation and reputation monitoring
  • Social scheduling and publishing
  • Inbox and calendar sync with Gmail or Outlook
  • QuickBooks sync
  • Bulk SMS campaigns

Review generation and inbox sync are both in progress. Social publishing is deliberately not being built: it is a product of its own and no trades business is choosing an operating system for it.

See whether it fits your business

Oleera is onboarding a small number of businesses at a time, so setup is done properly rather than left to a help article. Tell us what you run and we will tell you honestly whether it is a fit.

Request access Sign in