Four moves across the board
Each one is a drag or a click, not a form.
It lands
You add a lead, or a requirement you bid on arrives on its own.
You move it
Site visit, then proposal. Moving a card logs the stage and opens the task it implies.
You source it
Raise quote requests from the card, with the customer and capacity already filled in.
It becomes a project
Convert the card and it carries into delivery — contract, crew and handover.
A pipeline that knows what you won
A generic CRM is a list of names you maintain by hand. This one is wired into the work: when a bid is accepted or a project moves a stage, the board already knows.
- Offline leads and platform bids sit on the same board, not in two systems
- A project’s real stage drives its card — nobody keeps the two in sync
- Moving a card creates the task that stage calls for
- Quote requests go out from the card, carrying the customer and the capacity
- Convert a won lead and it opens as a project with its contract and crew
- Search and sector filters, on a board or a list — whichever you read faster
Lead
Added by you, or bid on here
Site visit
Measured and qualified
Proposal
Designed, calculated and sent
Procurement
Quote requests and orders
Installation
Crew on site, then handover
What EPCs ask about the CRM
Mostly whether it duplicates what they already keep.
Something not answered here?
Talk to usOne account, all of it
These are not separate products. They are the stages of the same job, and they hand off to each other.