MeloJobs · Solutions

What the Pipeline Is For.

Every lead from every source in one list, every deal on a board you shape, the paperwork and the money on the job, and the follow-up done by a workflow — each of the things that does for a contractor, on its own row.

01 · Leads

First Responder Wins the Job.

Every source — your hosted request forms, Google LSA, Angi, Thumbtack, Zapier, the ones you type or paste in — lands in Contacts with a clock on each waiting lead, read against the target you set: 5 minutes, 15 minutes or an hour. Responses are logged against the lead, so you can see how fast the shop answers.

  • One list, every source
  • A clock on every lead, against your target
  • Response time logged per lead
02 · Marketing

Which Source Pays for Itself.

Put a campaign's spend against its source and Marketing reads cost per contact and return on spend by source — from the contacts and the won deals already on the board, not a spreadsheet you keep. The Lead forms page shows each form's link, its contacts in the last 30 days and the share that became deals.

  • Cost per contact and return on spend, by source
  • Spend recorded on the campaign
  • Revenue read from the deals you won
03 · Scheduling

The Estimate Visit, Booked From the Lead.

Book the visit from the lead, the deal or the calendar — Day, Week or Month — and drag it when the day changes. One tap when you leave: On my way is stamped on the appointment and logged on the job, so the visit and its outcome are on the job's timeline.

  • Appointments on the job and on the calendar
  • On my way, stamped and logged
  • The visit on the job's activity
04 · Money

What Is Owed, by Status, From One Screen.

Acceptance creates the deposit; the invoice records what was paid against it. Payments is a board and a list of every payment by status, with Request Payment on the record, so what is owed is chased from one screen rather than found in three — and the client pays in the portal or on the link they signed.

  • The deposit created on acceptance
  • Payments recorded against the document
  • Every payment by status, requested from the record
05 · Clients

Every Address, One Client.

A client is one record with the properties under it, so a landlord's buildings are jobs on one profile — Overview, Projects, Payments, Calendar and Notifications where they belong, and one portal link for the lot.

  • Properties under the client
  • One profile, every job
  • A portal link per client
06 · Automation

The Follow-Up Nobody Has to Remember.

Six triggers start the workflows in the library — a waiting contact, a quote quiet for a day, a payment three days overdue — and their steps create the task or send the email, once you've set up an email sender. Test runs a workflow dry, writing and sending nothing; Run now runs it for real whenever you press it, and opening Home runs it too, at most every six hours.

  • 11 premade workflows, three of them waiting on a text number, MeloPay or partner workflows
  • Tasks, emails and review requests as steps
  • A dry run before it's on
07 · The team

Office on the Desktop, Trucks on the Phone.

The same jobs on two shells: a sidebar and a board for the office, five tabs and a day view for the crew. Teammates have roles — owner, admin, estimator, field — and a commission plan if you pay one; the subs, crews and suppliers you work with are kept in Partners, with a sub's or supplier's insurance expiry showing.

  • Roles and commission plans on the team
  • Partners with insurance-expiry status
  • One account, every device

Leads In,
Jobs Won

Every lead from every source lands in one pipeline, and one click turns a won deal into a signed quote.