The questions US and Canadian businesses ask when evaluating specialist Access design against marketplace hiring — answered directly.
What makes you different from hiring on Upwork or Toptal?+
On Upwork or Toptal, you hire an individual and manage the risk yourself — vetting their approach to normalization, error handling, documentation, and SQL migration planning falls on you. We are a specialist firm: we have built and documented 300+ Access systems for US businesses over 15 years, and every engagement includes schema design, VBA with proper error paths, run-log tables, FE/BE deployment packages, and a SQL migration roadmap. When we hand off, your IT team can govern the asset. When a marketplace freelancer finishes, you often have a working demo and a black box.
How do you price Access design work — hourly or fixed?+
We scope after a short discovery call where we map your data structure, concurrency requirements, reporting needs, and any existing system we're inheriting. From that, we provide milestone-bound fixed ranges — not open-ended hourly billing that grows with scope creep. You know what Phase 1 costs before we write a line of code. Emergency fixes on inherited broken systems are billed differently; we'll be clear about that up front.
Can you fix a database another freelancer built and left undocumented?+
Yes — this is one of the most common engagements we take on. We inventory every object (tables, queries, forms, reports, VBA modules), identify what's structurally broken versus what's just cosmetically rough, and stabilize before extending. When the inherited design cannot be rescued — usually severe normalization failures or VBA with global state that cannot be safely untangled — we say so clearly and propose a controlled rebuild with a SQL Server backend path. We don't polish broken foundations.
How long does a typical Microsoft Access database design project take?+
A ground-up small business database (3–6 tables, 2–4 forms, 2–3 reports, basic VBA automation) typically delivers in 2–4 weeks. Mid-complexity systems with multi-user concurrency, complex reporting packs, and SQL Server backend planning run 4–8 weeks. Legacy modernization (inheriting and restructuring an existing system) depends on what we find — we scope it after an audit. We ship in waves: first working slice, then multi-user hardening, then deployment packaging, so your operations are never hostage to a single big-bang launch.
Do you work with businesses in specific US industries?+
Our US client base spans distribution and logistics, regional manufacturing, financial services (back-office operations), healthcare administration (non-clinical data), field service companies, and professional services firms. The common thread is operational data that multiple staff members need to enter, query, and report on reliably — and where Excel has already proven too fragile. We're based in the US and work across all time zones.
Is our database design SQL Server–ready if we outgrow Access?+
Yes — that is a delivery requirement, not an optional add-on. We model primary keys, enforce referential integrity in-engine, design query boundaries to minimize ODBC round-trips, and document which objects would move server-side first in a hybrid or full upsize. When your writer count or data volume justifies SQL Server or Azure SQL, you migrate data and constraints without reinventing your entire natural key structure. We build the migration path into the design so growth is planned — not a panic rewrite.
What does your documentation handoff include?+
Every engagement includes: a schema ERD with table and field definitions, VBA modules commented at procedure level with purpose and parameter notes, a front-end deployment package (per-workstation .accdb with ODBC strings documented), a backend deployment package (server .accdb with instructions for IT), a tblRunLog or equivalent for automated process auditing, and a change log. The goal is that any competent Access developer — or your internal IT team — can maintain and extend the system without calling us for every small change.
