Straight answers

The back office every company runs on: bills and approvals, company cards and receipts, the QuickBooks sync, people and HR, files and documents, and an audit trail and access control over all of it.

On top of that sit the industry modules: bids, daily logs, plan sets and draws for construction, an online store for retail, proposals and billable hours for software development and design, and more. Every module is included in the price. It isn't your accounting system. Approved bills are handed to the one you already use.

No. The back office doesn't care what the company does. Bills, approvals, cards and receipts, documents, people and access work the same way whatever the business is.

Then each industry gets its own modules on top: construction, retail, software development, design and non-profit today. Pick your industry when you set up and its modules come on together; anything else is one switch away.

Certificates and expiry dates are held per vendor, so a policy about to lapse surfaces before it does rather than after. It reflects the documents in your account, it isn't a substitute for obtaining a current certificate, and nothing about it is a guarantee against a carrier cancelling a policy mid-term.

No, and we'd be suspicious of anyone who told you to switch general ledgers mid-year. Your accounting system stays your book of record and your accountant keeps working the way they already do.

Cordwyn is where the bill gets read, coded, argued about and approved. That's the work a general ledger was never built for. The approved bill is then handed to your books, and a person does the posting.

You correct it, and the correction becomes history the next match learns from, so the same vendor lands in the same category next time.

More importantly, the system is built to decline rather than guess. If two of your locations sit on the same street and the invoice doesn't carry a unit number, the cost is left unassigned and flagged for a person. A blank field costs you thirty seconds. A confident wrong answer puts the cost on the wrong location or the wrong client's invoice, and that's a trust problem, not a bookkeeping one.

No. Vendors receive requests and documents by email. Clients reach what you've shared with them through an emailed link rather than a password they'll have forgotten by the next billing. That matters more than it sounds. A portal your client can't get into is a portal that generates phone calls.

Yes. Share links are scoped to the sections you pick. You decide whether a client sees the cost detail, the documents behind each line, photos, the schedule, or only the billing summary. Views are logged, so "I never got that" has an answer.

That's the assumption it was built under. The field surfaces (daily logs, time entry, receipt capture) are the light ones, and the phone layout gives someone out in the field the same destinations an admin gets on a desktop rather than a stripped-down subset of them.

Access is a named profile, plus per-project assignment, plus per-user overrides. Finance, company cards, executive review and business development are each gated separately, so a project manager with full access to their three projects still can't open the card statement.

Every table carries an organization column with row-level security policies enforced by Postgres itself. The isolation doesn't depend on the application remembering to filter, which is the failure mode that actually matters in shared systems.

Yes. Bills, invoices, documents and photos export on request in a machine-readable format, during your subscription and for 90 days after it ends. Leaving should be a task, not a negotiation.

Row-level changes are captured append-only, so you can see who changed what and when, and put a bad edit back. Unusual bursts of activity raise an alert rather than waiting to be noticed.

Yes. Each company is set up on its own, with its own vendors, people, documents and approvals. A bill coded in one company doesn't turn up in the next one's numbers.

Each company stays its own company. You just stop running its back office from scratch.

It doesn't matter. Every company runs on the same foundation, and each one switches on the industry modules that fit it. A builder and a retail brand under one login each get their own set. The people who work across your companies don't relearn the system every time they cross a company line.

Yes. Each company keeps the accounting system it already uses, and approved bills are handed off for a person to post. We add accounting connections as our customers need them.

Each company has the same approval queue and the same outstanding tracker, so what's waiting and who the holdup is becomes something you look up instead of chase.

It isn't a consolidation. Cordwyn doesn't produce consolidated statements or move money between companies.

$500 a month for your first company, $200 for a second and $150 for each one after, with unlimited users and every module included. No setup fee, cancel anytime, and the first 30 days are refundable in full. Full pricing.

Yes, company by company. Imports run in batches so you can check a slice before committing the rest, and there are merge tools for the duplicate vendors every real migration turns up. Categories and vendor-to-category mappings come along too, which is what makes the automatic coding useful in week one instead of month three.

Most offices are coding live bills the same week they import. The honest constraint isn't the software. It's how quickly your team stops emailing invoices to each other out of habit.

A person who built it, reachable through the same list you joined rather than a ticket queue.