Why generic tools tend to fall short
Architecture is a project business with billing models that don't look like anything else. A retail product gets sold once. A SaaS contract gets billed monthly. An architecture project lives for one to three years, gets billed in phases, runs against a fee schedule, and usually drags consultants along with it. The financial model is nothing like the businesses most software was built for.
Generic PM and accounting tools handle the surface (tasks, invoices, hours), but the parts that actually matter on an architecture project — phase budgets, percent complete invoicing, sub pass-through, fee burn against the schedule — either don't exist or have to be wedged in through custom fields and spreadsheets that someone has to keep alive.
That's why firms eventually move toward software built for the industry. Not because the features list is longer, but because the defaults match the work.
What to actually look at in a demo
Forget the feature checklist for a minute. The questions worth asking are the ones that map to how your firm runs projects.
Phase and task budgeting
Can you set up phases the way your contracts read, allocate fee per phase, and break a phase down into tasks if you need to? Does budget vs. actual update as the team logs hours, or is it a separate report that someone has to refresh?
Timesheets that don't fight you
Time entry is the data layer everything else sits on. If timesheets are slow or annoying, you get bad data and the rest of the system is downstream of that. Look for fast entry, mobile, and a clear path from a logged hour to the budget it lands against.
Invoicing that understands fee schedules
AIA G702/G703 style invoices, percent complete by phase, retainers, additional services, retention. If the answer involves “you can export to a template”, you're going to spend the next three years exporting to that template.
Consultant workflow
Most projects have subs. How does the software handle their invoices, how do they get reviewed and approved, how does that flow into your client invoice as pass-through? If the answer is “email and attachments,” nothing has actually been solved.
Reporting at the firm level
Utilization, fee burn, project margin, AR aging. The principal needs to glance at a dashboard and know what's on fire. The PM needs to drill into the project. Both views should come out of the same data.
Things that should make you nervous
- Marketing aimed at “all project-based businesses”. Translation: the team building it doesn't live in your industry.
- No native phase budgets. If phases are a custom field, you're going to be building the workarounds yourself.
- No sub workflow. Sub coordination is half the job on most projects. A platform that ignores it is missing a leg.
- Six months of implementation for a 15-person firm. Enterprise tools can do everything but they cost more in onboarding time than most small firms can afford to lose.
- No demo with your data. If the vendor won't set up one of your real projects in a demo, you're going to be the one finding the gaps after you've signed.
Questions worth asking, in order
- Walk me through setting up a project with the phases and tasks the way our contract is written.
- A designer logs four hours on schematic floor plans. Show me what updates and where.
- We have a structural sub. Show me their invoice coming in, getting approved, and showing up on the client invoice as pass-through.
- Generate an AIA-style invoice with three phases, retainer applied, and one line of additional services.
- Show me a firm dashboard: utilization, AR aging, project margin across all active jobs.
- For a firm our size, how long until we're actually using this in production? Who owns onboarding on your side?
- What happens when we hit an edge case six months in? Email, Slack, phone? Same day or next week?
Where Archflow fits
Archflow is built for architecture firms specifically. The feature set covers the workflows firms actually run on: phase and task budgets, timesheets that connect to those budgets, invoicing that understands fee schedules, a sub portal, and dashboards at both the project and firm level.
It's not enterprise-heavy. The setup for a small or mid-sized firm runs in days, not quarters. In a demo, the Archflow team will set up one of your active projects so you can see how it would look on a job you already know cold.
If you're weighing options against other architecture-focused tools, come at the evaluation with a real project in mind and questions you already know are hard. The right answer should be obvious in the demo.
When you're ready, book a demo. Bring your messiest project.