Eleven departments on one data model. A quotation becomes a contract, a contract opens a project, a project raises requisitions and bills — and none of it is re-typed, because it is all the same record.
Permissioned to the row
Access is resolved once, per person, per studio. No role means nothing — there is no fallback that quietly grants more. A manager scoped to a department sees that department and everything under it, and nobody can grant a right they do not hold themselves.
Arabic and English, mirrored properly
Not a translation layer over an English product. Direction, typography and the component library all mirror, and a person picks their own language rather than inheriting the company's.
Live, without refreshing
A change made by one person appears for everyone looking at the same records. Reconnecting replays what was missed rather than losing it.
Your data stays yours
Every record belongs to one studio and is fenced at the database, not merely filtered in the application. Files are served only after the same membership check the screens use.
Every one of these is built and running today. Nothing on this page describes something you cannot open.
Leads, deals and the board they move across. Customers with their own page — what they have bought, what is open, what was won and lost, and the rates they were promised. Quotations price from those rates rather than from cost, and a won quotation becomes a contract with its variations tracked against it.
Tenders sorted by deadline rather than by entry date, because most end in a decision not to bid and recording only the winners loses the ability to say what you keep losing. Bills of quantity priced against a reusable rate library, a tender pack whose reissues never overwrite what you priced against, and a signature required before a bid is submitted.
A plan with dependencies, durations and a critical path. A cost breakdown that says what the job is allowed to cost, what has been ordered, what has been invoiced, and how far the work has actually got against all three. Billing milestones and retention on the other side of the same project.
The controlled document register — drawings and specifications, their revisions, and who has seen which. A superseded revision is marked rather than deleted, because what you built against has to stay answerable afterwards.
A purchase requisition is the first document that can be refused cheaply, before there is a commitment. Approved requests convert to orders, suppliers are rated on what they actually delivered, and subcontracts carry their own scope and valuations.
Stock across locations, with what has been ordered, what has arrived and what was rejected on receipt. Serial and batch tracking where the item needs it.
Jobs dispatched to people who are not at a desk, the shifts they work, and the site reports they file. Permits where the work needs one.
Deliveries, the vehicles that make them, and what each trip cost. Fleet servicing scheduled against the vehicle rather than the calendar.
People, their departments, and the roles that decide what they may open. Leave that respects the org chart, and timesheets that reach a project's costs.
Invoices, bills and the accounts they post to. Bills above a limit you set need a second signature, and the exchange rate that routed one is stored on it, so a rate moving overnight cannot re-route a bill already mid-approval. 166 currencies with daily rates.
Who is in the studio, what each role may reach, the org chart, locations, and the settings the rest of it reads. Roles are departmental — a Site Engineer is offered to a site department, not to a sales one.
Free for teams of one to nine
Start free