Reporting
The numbers the rest of it exists to produce — read by department, not blended into one line.
- P&L by department
- Revenue and pipeline
- Commission
- Labor cost
- Exports
VenWeave is the ERP for event services, built for the venue and the vendor to run it together. Quote it, staff it, invoice it, and see the margin by department — with venue commission, crew hours and food and beverage in the same system as the money.
Running in production every day inside a working AV production company. Now opening to a first group of outside customers.
Illustrative figures
Which is useful, and it is not the question that decides whether you had a good year.
Built around the warehouse. They answer:
Built around the deal and what it returns. It answers:
See how this holds up against a named competitor, line by line: LASSO · Rentman · IntelliEvent
Not a suite of products that integrate. One database, so a crew member's hours reach the department P&L without anybody exporting anything.
The numbers the rest of it exists to produce — read by department, not blended into one line.
The pipeline from inquiry to paid, including the client-facing side.
What you own, what it rents for, and what it costs to put on a floor.
Catering priced and costed the same way as equipment, in its own department.
The property relationship, including the commission that comes off the top.
Scheduling and the record-keeping that follows it, from clock-in to review.
You own kit, you send crews into venues, and somebody takes a commission off the top. This is the shape the product was built inside, so it understands the job from the vendor's side.
You run AV, banquets or both in-house, and outside vendors work your property under a preferred-vendor list. Read AV and food and beverage as separate departments with their own P&L, not one blended line.
You subcontract more than you own, so vendor cost and margin per event matter more than a warehouse count. Same money model, less of the inventory.
You need quoting, clients, venues and clean documents without the depth of a production company's back office. Start at the lighter tier and grow into it.
Vendors. Venues. VenWeave.
Most of these are the reason a growing company outgrows the tool it started on. They are in the foundation here rather than on a roadmap.
The venue's rate is captured the moment a quote is signed or invoiced, not read live off the venue after. A city raising its rate next quarter does not reach into a document a client already agreed to — the one exception is a tax-exempt client, recorded as a flag, not a typed zero.
Commission is rated per revenue category — product, labor, other — and frozen onto the event the moment it confirms. The venue's live rate can move after that; the confirmed event does not move with it.
Pay rate lives on the assignment, not just the person. The same technician can work a load-in at one rate in the morning and a show call at another that night, and both post correctly to their own event.
Labor bills hourly or by day rate, line by line. Catering bills per person, per item or flat. All three sit on the same line-item schema and the same document — nobody works around a mismatch by hand.
A quote can be billed in the client's own currency, fixed to a published exchange rate the moment it becomes binding. A payment settled later, in a different currency, is measured against that same document at its own date — the gain or loss is a number, not a shrug.
Features are grouped by the kind of business that needs them, so you are not paying for a commission engine you will never open.
Meeting planners and coordinators.
AV, production and event companies — and venues running their own.
Groups and multi-property operators.
Volume-based pricing available in place of part of the seat fee.
Talk about EnterpriseThe questions that come before moving a back office onto something new — answered plainly, including the ones where the honest answer is not yet.
Clients, venues, equipment and your catering menu import from a spreadsheet — .xlsx or .csv, matched by column header, not a fixed template. Events import too, from CSV, and bring their client and venue with them; a row with a dollar figure on it becomes a quote and an invoice, not just a date on a calendar. Timesheets, employees and quotes already in flight do not have an importer yet — those get entered by hand during setup.
We do not have a number to give you — every organization on VenWeave today is us. What is true: the imports above cover clients, venues, equipment and your menu on day one, and everything else gets typed in by you or by us while we watch for whatever the importer should have caught and did not.
You do. Today that means CSV, one report at a time — revenue, P&L, operations, receivables, invoices, the audit log — not one button that hands you everything at once. If you need more than the reports cover, ask and we will pull it by hand.
No escrow agreement and no contractual data-return clause exist today — a real gap for a product with one customer, and naming it here is more honest than waiting for you to find it. The exports above work for that reason as much as any other; if your organization needs something in writing beyond that, raise it before you sign.
To view what you share, yes — no account, no login, just the link, and pricing is never in the payload. To write back on the note thread attached to it, they need an account of their own; there is no signup built into the share link itself, so a venue or vendor not already on VenWeave can see everything you sent but cannot yet reply from inside it.
Business hours, best effort — the same line already on this page below. There is no support SLA and no guaranteed response time. If your operation needs one in writing, raise it before you sign rather than assume it from a word like support.
Not today. No QuickBooks, no Xero, no general-ledger export. If reconciling against one of those matters to you now, say so — it tells us which one to build toward first.
No accounting-system integration. No bulk import for timesheets, employees or quotes already in flight. No single button that exports everything at once. No self-service way to delete an organization outright — the destroy route was removed on purpose, not left out by accident, because Organization sits at the root of 34 cascade relations, and a self-serve delete there takes an entire tenant's data with it. No formal support SLA.
No number on this page, on purpose. Three tiers, priced per organization and per seat, with volume pricing available on Enterprise in place of part of the seat fee. What it actually costs depends on how many organizations and how many people are logging in — a five-minute conversation, not a slider.
We are taking on a small first group of outside customers so we can build against real operations rather than assumptions. Send a line about your business and we will show you the parts that matter to it.
Business-hours support, best effort, and a straight answer about what is not built yet.
Tell us what you run today and we will show you the parts that matter to it.
Or email info@venweave.com directly.
Tell us what you run today — the kit, the crew, the properties — and we will show you the parts that matter to it.
Or email info@venweave.com directly.
Tell us about the group: how many properties, how many people, and what your books need to separate.
Or email info@venweave.com directly.
Tell us what you run today and we will show you the parts that matter to it.
Or email info@venweave.com directly.