For contractors, architecture and interior design teams, manage project opportunities, quotes and tasks in one place. Keep long sales cycles under control with staged pipelines.
The modules that matter most for your industry work right out of the box.
Pipelines, kanban, scoring, saved views
Stages, products, revenue & win rate
Recurring tasks, project boards
Income & expense, commissions, reports
Catalog, stock movements, alerts
Pivot reports, funnel, team performance
Construction sales are slow, expensive to quote and easy to lose in the gap between "quote sent" and "contract signed". An enquiry for a kitchen, an extension, a roof or an off-plan apartment takes weeks or months to close, every step costs a site visit or a drawing, and the job that wins is usually the one that was followed up. So the setup for a contractor, installer or developer is a pipeline whose stages are events (site visit done, proposal sent, contract signed), idle alerts on the proposal stage, materials as products with cost prices so that a won job deducts stock and books its cost automatically, expenses recorded per job, and a project with tasks that opens the moment the deal is won. It is the commercial layer of a building company — not estimating, scheduling or accounting software.
A homeowner fills in a web form about a loft conversion, a facilities manager phones about re-roofing a warehouse, a couple walks into a sales office asking about a two-bedroom unit in a block that will be finished next year. All three have already spoken to somebody else. All three will be quoted by two or three companies, and the quotes will be within ten percent of each other. What decides the job is rarely the number; it is who visited first, who sent the proposal when they said they would, and who called back after it went quiet.
Speed matters even here. The Harvard Business Review study of 2,241 companies found that responding within an hour made a lead nearly seven times as likely to be qualified than waiting even an hour longer, and that the average response time was 42 hours. A building company is not slower by nature; its estimator is on a roof when the form arrives, and the enquiry waits on a phone until Friday.
The second shape is cost per step. A site visit is half a day; a proposal with drawings is a day or two of an estimator's time. A company that visits everyone and follows up nobody spends its margin on quoting. The pipeline exists to make sure the expensive steps are spent on enquiries that are qualified, and that every proposal is chased until it is won or honestly lost.
Each stage below is something that verifiably happened. "Thinking about it" is not a stage.
| Stage | Verifiable event | Automation that usually helps |
|---|---|---|
| New enquiry | Form, call or message received | Assign owner; task "call within the hour" in working time |
| Qualified | Budget band, address and timing recorded | Required fields on stage entry; below budget floor → polite decline template |
| Site visit booked | Appointment with date, address and surveyor | Reminder the evening before; travel time on the calendar |
| Site visit done | Appointment marked attended, measurements attached | Task "proposal due" 3 working days later |
| Proposal sent | Proposal amount recorded, file on the record | Follow-up at 3 and 7 days; idle 14 days → alert manager |
| Negotiation | Revised amount or scope recorded | Revision counter as a field; manager approval above a discount |
| Contract signed / Lost | Deposit received, or explicit refusal | Deal won → project opened, stock deducted, cost booked; lost reason required |
The stage that leaks is proposal sent. Fourteen days of silence on a proposal is not "still deciding"; it is a competitor's site visit. Put the idle alert there before tuning anything else. Kitchen and window installers usually add a "showroom visit" stage before the site visit; commercial contractors add "tender submitted" and "clarifications" between proposal and negotiation. Starter includes two pipelines, Growth five, Business ten — enough for residential, commercial and maintenance as separate processes.
| Field | Type | Why |
|---|---|---|
| Job type | List: extension, roof, kitchen, windows, full build, maintenance | Routes to the right estimator; the main report dimension |
| Site address | Text | Different from the client's address more often than not; drives visit planning |
| Budget band | List | Qualification; decides whether a site visit is worth it |
| Desired start / deadline | Date | Date-based automations: "start minus 30 days → order materials task" |
| Proposal amount / revision | Number | Pipeline value before a deal; how many times you re-quoted |
| Architect / referrer | Text or list | Where the good jobs come from; referral commissions |
| Ad campaign / ad set / ad | System fields | Filled by the lead webhook; tells you which ad produced contracts, not clicks |
| Lost reason | List, required on Lost | Price, timing, chose a neighbour's builder, project cancelled — the only way to learn |
The lead-detail layout is configurable per role: the office sees contact and site fields, the estimator sees measurements and proposal fields, the owner sees margin. Nobody sees forty inputs at once. Tags handle the things that do not deserve a field — "planning permission pending", "listed building", "access difficult".
A site visit is an appointment with an address, a surveyor and a client, booked from the record or straight from the WhatsApp thread where the homeowner sent the photos. It sends a reminder the evening before — by WhatsApp, SMS or e-mail — and its outcome moves the pipeline. Marking it attended opens the "proposal due" task; marking it no-show opens a rebooking task instead of losing the enquiry.
The shift calendar decides which surveyor is bookable on which days, so a Tuesday visit is not given to someone who is on a site in another city on Tuesdays.
Windows, doors, boilers, tiles and kitchen units are products in the catalogue, each with a sale price, a cost price and whatever custom fields the trade needs — width, height, glazing, colour, supplier code. A deal lists the products in the job. When the deal is won, the stock of each product is deducted and its cost is booked as a cost-of-goods expense automatically, so the margin on the job appears without anyone typing it.
Product custom fields show as columns on the product list and can be edited in the cell, which is how a small merchant keeps its catalogue current between deliveries.
On the Business plan, a won deal can open a project: the client, the site address and the products come across, and a task list follows — survey confirmation, materials order, scaffold, first fix, second fix, snagging, handover. Tasks have owners, due dates and, where the work repeats, a recurrence; a weekly site report is a recurring task, not a reminder somebody sets each Friday.
Projects are where the office and the site meet. The site manager sees today's tasks on the project; the office sees which projects have overdue tasks; the owner sees how many projects are open and which one is quietly late. Flow Boards — an infinite whiteboard on Growth and above — are used by some teams for the site sequence sketch that would otherwise live on a wall.
This is not a scheduling engine. There is no Gantt chart, no resource levelling and no critical path. Companies that need those keep their planning tool and use the project here for the client-facing list of what was promised and whether it is done.
Construction margins are made or lost on the job, not on the year. The finance module records income and expenses; a won deal creates its income, materials create their cost-of-goods expense, and anything else — skip hire, a subcontractor invoice, a parking fine — is entered against the same deal. Deal profitability, on Business, then shows revenue, cost and margin per job and per job type.
None of this replaces accounting. There is no ledger, no VAT return and no bank feed. It answers one question the accounts cannot: which jobs, job types and salespeople actually make money.
A developer's sales office is a different animal: hundreds of enquiries from ads and portals for a fixed inventory of units, a cycle measured in months, and a hard question — which ad produced reservations, not visits. Units are products with a cost price (land and build cost apportioned) and custom fields: block, floor, orientation, size, view. A reservation is a won deal; the unit's stock goes from one to zero, and the cost of goods sold is booked, so project profitability shows the real margin as the block sells through.
Campaign, ad set and ad are system fields filled by the lead webhook. A pivot report of campaign by stage shows which ads reached "reservation" and which produced only sales-office visits. Country and language are filled from the phone number's country code, which is how a sales office selling to buyers abroad routes German-speaking enquiries to the German-speaking consultant automatically, and why each user has their own display time zone.
Permissions are per module and per action — view, create, edit, delete, export — and data scope is own, department or all. The activity log, from Growth, records who changed a proposal amount, who exported the client list and who reassigned a lead, which is the conversation that happens when an estimator leaves for a competitor.
This is not estimating, scheduling or accounting software. It does not take off quantities from drawings, produce Gantt charts, level resources, run payroll, file VAT or connect to a bank. It does not manage BIM models or hold building-regulation documents as a system of record. Keep the planning tool and the accountant; put the enquiry, the visit, the proposal, the chase, the job's margin and the client-facing task list here.
It is also worth saying plainly that automated daily backups of your workspace are not currently part of the service, and that contracts are not signed electronically inside it. Export what you must retain, and attach the signed contract as a file.
| Symptom | Most likely cause | Fix |
|---|---|---|
| Proposals go quiet and die | No idle rule on the proposal stage | Idle 14 days → alert owner; follow-up tasks at 3 and 7 days |
| Everyone gets a site visit | No qualification stage; budget never asked | Required budget band and job type before "site visit booked" |
| Margin is a surprise at year end | Materials without cost prices; expenses not tied to deals | Cost price on every product; job expenses against the deal; profitability report |
| Same client twice | Filled the form, then called from another number | Duplicate report matches phone endings; merge |
| Ad reports say leads, office says none | Ad fields empty on webhook leads | Map campaign, ad set and ad in the webhook; they are system fields |
| Estimator took the pipeline when leaving | Records owned by the person, no manager scope | Department scope; bulk reassign; export permission for managers only |
| Site manager edits proposals | Given administrator instead of a role | A Site Manager role with projects and tasks only |
| Module | Starter | Growth | Business |
|---|---|---|---|
| Leads, pipelines (2 / 5 / 10), custom fields, tags, saved views | Yes | Yes | Yes |
| Site-visit appointments with reminders | Yes | Yes | Yes |
| Products with cost price, stock deduction, CSV import | Yes | Yes | Yes |
| Income, expenses, commissions | Yes | Yes | Yes |
| Tasks, recurring tasks, web forms, lead webhook | Yes | Yes | Yes |
| Automations (idle alerts, follow-up tasks, routing) | — | Yes | Yes |
| Departments, full roles, activity log, pivot reports | — | Yes | Yes |
| Flow Boards | — | Yes | Yes |
| Projects with task lists from won deals | — | — | Yes |
| Deal profitability per job | — | — | Yes |
A two-person renovation firm quoting from the van runs on Starter. An installer with an office, two surveyors and ad-driven enquiries lands on Growth for the idle alerts and the roles. A contractor or developer who wants a project opened on every won deal and margin per job needs Business. See the pricing page, and the products and projects pages for the two modules that carry the load.
Set up your workspace in under a minute — free for 14 days.
Create your workspace