Client documents move by email
Contracts, statements and drawings travel as attachments across personal inboxes. Nobody can say which version is current, who opened it, or when. A portal with versioned files and access logs replaces the thread.
Industries · Professional Services
Digital Systems for Professional Services Firms
Law, accounting, engineering, architecture and consulting firms run on documents, matters and trust. We build the portals, intake systems and publishing tools that make that work visible to clients and easy for your people.
You own the code and IP Weekly demos Reply within one business day
Portal
Members
Directory
Documents
Roles
Audit log
Search members, roles or centres
Single sign-on
MemberRoleLive
Admin
Member
Board
Member
1,284
Members
99.9%
Uptime
0
Access issues
Professional Services, in short
OlDevs is a full-stack technology studio in Vancouver, British Columbia that builds websites, client portals and internal systems for professional services firms.For law, accounting, engineering, architecture and consulting practices we handle secure document exchange, matter and project intake, proposal and knowledge systems, and publishing for articles and firm commentary. Every build ships with WCAG 2.2 AA accessibility, clear access rules and full client ownership of code, designs and accounts. Request a quote to scope the work.
Key facts
- 01term
- value
- 02term
- value
- 03term
- value
- 04term
- value
- 05term
- value
- 06term
- value
Professional Services
What professional services firms bring us
The problems we are asked to solve most often — and how.
Intake is a PDF form and a phone call
New matters and projects arrive with missing conflicts information, no scope and no file references. Structured intake with conditional questions, identity checks and routing rules gets the right partner the right brief on day one.
Expertise lives in people, not systems
Precedents, model clauses, calculation sheets and past proposals sit on individual desktops. When a senior person is away, the firm rebuilds work it has already done. Searchable knowledge systems keep that value inside the practice.
Proposals are rebuilt from scratch
Every pitch restarts in a word processor, so scope language, bios and case summaries drift apart. A proposal system with approved components, version history and export keeps submissions consistent without flattening the argument.
Confidentiality limits what you can ship
Privilege, client confidentiality and professional obligations shape where data can sit and who may see it. We design roles, retention and residency into the build, and document decisions so your risk committee can review them.
Long buying cycles hide what works
A retainer may close a year after the first article was read. Without connected forms, calls and CRM records, marketing gets judged on form fills alone. We wire the trail from first visit to signed engagement.
Process
How an engagement runs
Discovery
We sit with partners, practice managers and the people doing intake to map matters, documents, approvals and the places work currently stalls.
Architecture and design
Data model, access roles, retention and interface design are agreed together, because in this sector who can see what is a design question, not a setting.
Build in weekly increments
Development runs in short cycles with a working demo each week, so feedback lands while changes are still inexpensive.
Review and launch
Accessibility, security and content review before release, then a staged rollout with training material written for your staff rather than for developers.
Support and iteration
After launch we monitor, patch and extend. New practice areas, new intake paths and new reporting get added as the firm changes.
How we work
How OlDevs works with professional services firms
01
One accountable team
The people who scope the work build it. You get named engineers and a single point of contact rather than a handoff chain between sales, delivery and support.
02
A working demo every week
You see the real thing running each week, not a status deck. Partners and practice leads can click through the portal or intake flow before the decisions harden.
03
Security decisions written down
Roles, retention, logging and hosting region are chosen deliberately and recorded in plain language, so your risk lead or general counsel can review them without reading code.
04
Intake modelled on how you take work
We map how enquiries actually reach you: referrals, direct calls, RFP portals, existing clients. The forms and routing follow that reality instead of a generic contact page.
05
Content systems your people will use
Editors get structured templates for articles, bulletins, bios and case summaries, with approval steps that fit how a firm signs off on published views.
06
Measurement that survives a long cycle
Forms, calls and CRM records are connected so a signed engagement can be traced back to its origin. We report qualitatively on what is working and what is not.
Recommended
Where we’d start
Since 2014
Studio founded in Vancouver, British Columbia
Weekly
Working demo through the build
WCAG 2.2 AA
Accessibility standard we build to
FAQ
Professional Services — questions we hear first.
Yes. We build portals with role based access, versioned document exchange, granular sharing, activity logs and single sign on where your identity provider supports it. Scope depends on how your matters, entities and client groups are structured, so we map that first. Request a quote to start.
We work with law, accounting, engineering, architecture and consulting practices. The patterns overlap: confidential documents, structured intake, conflicts or independence checks, deadline pressure and long referral driven sales cycles. We adapt the model to your regulator and your practice areas.
You do. Clients own all code, designs, accounts and intellectual property produced in the engagement, including repositories, hosting, analytics and domain records. There is no proprietary layer you must keep paying us to use, and nothing to unpick if you move the work to another team or bring it in house.
We build with your obligations in mind: access control, retention rules, audit logging, encryption in transit and at rest, and hosting regions you choose. Canadian privacy law and your professional conduct rules may apply to the firm, and your counsel or risk lead makes those calls. This page is not legal advice.
We build to WCAG 2.2 AA as a default, not an add on. That covers keyboard navigation, colour contrast, focus states, form labelling, error handling and document structure. Public sector buyers often ask about it, and it matters for anyone reading a long report on a phone.
Often, yes. We start with a review of the code, hosting, data model and content, then tell you plainly what is worth keeping and what should be rebuilt. Sometimes the answer is a staged migration behind the existing site so your search rankings and client links stay intact.
We connect forms, calls, downloads and CRM records so a signed engagement can be traced back to the first article or search that brought the client in. Reporting is organised around qualified enquiries and matters opened rather than traffic alone, and we describe outcomes qualitatively, not as invented benchmarks.
Let’s connect
Tell us about your project.
We’ll reply within one business day with next steps and a tailored quote — no obligation.