Locations · Richmond, VA
Richmond agencies, banks, health systems and public bodies work with OlDevs for software that is built once and built properly. We deliver from Vancouver, meet on Eastern Time, and come to Virginia when a project needs it.
Remote from Vancouver, on-site when useful Weekly working demos Reply within one business day
$oldevs deploy --env production
✓Build passed · 212 tests · 0 warnings
✓Migrations applied · postgres 16
✓API v2 healthy · 142ms p95
→Rolling out to 3 regions…
Yes.Richmond businesses and public organisations hire OlDevs regularly, and we deliver remotely from our Vancouver studio with trips to Virginia when the work benefits from face to face time. The city is on Eastern Time, three hours ahead of us, which puts your afternoon against our morning for meetings. We cover websites, web apps, Android and iOS apps, full-stack development, AI development and performance marketing.
Key facts
Services
Seven services from one accountable team — delivered remotely in your working hours.
Built for Virginia
The local rules and realities we design for from the first call.
The Virginia Consumer Data Protection Act makes what you collect and who you share it with worth documenting. We list every field, remove anything nobody uses, record where data travels, and build the screens your staff need to action a consumer request. Your counsel decides what the act requires of you.
ADA Title III litigation risk applies to any public site, and the 2024 ADA Title II rule requires WCAG 2.1 AA for state and local government content by April 2026 or April 2027 depending on size. Section 508 governs federal work. We deliver WCAG 2.2 AA.
A Spanish version needs the same care as the English one. We choose the journeys that matter, translate the interface as well as the copy, mark the language correctly for search engines and screen readers, and leave the text editable in your own system.
For Virginia clients we normally host in United States regions and keep the database, uploads, backups and logs together in that region. The decision is documented before the build. Accounts, domains and repositories are registered to you and remain under your control.
Sectors
Public services need pages that anyone can read and forms anyone can finish. We write in plain language, design for low bandwidth and older devices, and treat accessibility testing as part of every sprint instead of a final gate.
Account portals, application flows and adviser tools where an error is expensive. We document the rules, test them properly, and design screens that tell people exactly what will happen before they confirm anything.
Directories, referral paths, appointment requests and internal tools built around what staff and patients actually do. We agree the data collected up front, keep it to the minimum, and make each step legible on a phone.
Freight and warehousing teams need tracking, scheduling and customer portals that stay accurate when volumes spike. We integrate with the systems already running your yard rather than replacing everything at once.
Process
Discover
A scoping call on Eastern Time, then a written summary of goals, users, integrations and risks. Before anything is built you know what the first release contains and who is accountable for it.
Design
We map the journeys, then design the screens and test them for contrast, focus order and plain language. Comments can be left on the prototype whenever suits your day, not only during calls.
Build
Engineering runs in weekly cycles with a demo you can open yourself each Friday. One team stays accountable throughout, so Richmond stakeholders always know who to ask.
Launch
Content, analytics, search and accessibility checks are finished before the switch, and we deploy into your own hosting with a rollback ready. Someone is available in your working hours that day.
Grow
We keep going after launch with SEO and content, paid search and social, email, and testing on the pages that carry the most traffic, reported monthly without spin.
FAQ
No, we do not. The studio is in Vancouver, British Columbia, where the whole team sits, and Richmond work is delivered remotely. We schedule calls in Eastern Time so nobody has to take a meeting at an awkward hour, and we travel to Virginia when a session is better held in person.
Yes. Section 508 applies to federal work, and the 2024 ADA Title II rule requires WCAG 2.1 AA for state and local government content by April 2026 or April 2027 depending on the population served. We build to WCAG 2.2 AA as standard and test with keyboard and screen reader as we go.
It shapes what you collect, how you explain it and how you respond when someone asks about their data. We keep collection minimal, write notices in ordinary English, log where information is passed on, and give your team a screen for handling requests. Your lawyers confirm the legal reading.
Yes, for a good part of the day. The three hour gap means our morning covers your late morning and afternoon, and that is where standing meetings sit. Outside it you can leave comments on the board or the prototype, and every enquiry gets a reply within one business day.
Often. Richmond has a strong advertising and professional services scene, and we build the software behind campaigns, products and client platforms while the agency keeps the client relationship. We can stay in the background or join client calls, whichever the agency prefers.
A description of the problem, who it is for, anything the new system has to connect to, and the date you are aiming at. That is usually enough for a first conversation, after which we send an approach and a written quote. Request a quote and we will reply within one business day.
Let’s connect
We’ll reply within one business day, in your working hours, with next steps and a tailored quote — no obligation.