How It Works — From Discovery Call To Delivered Workbook
Every Local Data Works build follows the same simple path: a short discovery call to understand your forms and workbook, a focused build phase, a live walkthrough at handoff, and an optional retainer for ongoing changes. The workbook stays as a local file you own at every step.
Step 1 — Discovery Call and Workflow Review
Every Local Data Works project starts with a short discovery call. We walk through the form or process you want automated, the workbook on the receiving end, and the people who actually open the file every day. The goal of this conversation is to understand the real workflow, not a generalized version of it. By the end of the call we know which forms feed which sheets, which fields matter, what reports the workbook needs to produce, and where data is currently being rekeyed by hand. From that conversation we draft a short written scope so the build is grounded in your actual operation rather than a template — and you receive a fixed quote before any work begins.
Step 2 — Workbook and Form Build
With scope approved, we build the workbook and the form-to-workbook connection. The workbook is structured around the way your team reads data — clear sheet names, consistent column layouts, validated inputs, and dashboards that surface the numbers you check most often. On the form side, we connect web forms, PDFs, email submissions, or paper intake into the right sheet of the workbook so submissions land as structured rows automatically. Throughout the build, the file lives as a local Excel workbook you own. There is no SaaS account, no platform login, no per-seat fee — the spreadsheet is the product.
Step 3 — Walkthrough, Handoff, and Documentation
When the build is ready, we walk through the workbook with you live. You see exactly how each form feeds the file, how validation behaves, how dashboards refresh, and how to make small future adjustments yourself. You also receive a short written reference covering the sheet structure, the form mappings, and the maintenance steps that keep the workbook healthy. Handoff includes the workbook file, the form connection setup, and any supporting templates — all delivered as files that live on your hardware, not in a vendor account that could disappear later.
Step 4 — Optional Ongoing Adjustments
Most operations evolve over time. A new form gets added, a column gets renamed, a dashboard needs a new metric. Local Data Works offers optional ongoing adjustment retainers for businesses that want a known person on call for changes after launch. These retainers are sized to the workload — some clients need a few small tweaks per quarter, others need monthly check-ins as their operations grow. Either way, the workbook never gets stuck waiting on a roadmap from a SaaS vendor; small changes happen on your timeline and stay inside the file you already own.
What a Discovery Call Actually Covers
A discovery call is not a sales pitch — it is a working conversation about how data moves through your operation today. We walk through the forms you currently use, where each one ends up, who looks at the resulting workbook, and what the workbook needs to produce in the way of reports, dashboards, or routine outputs. We ask the questions that surface the silent friction in the current process: which task takes longest at the end of the week, which numbers your team distrusts, which forms get skipped, which dashboards have stopped being updated. By the end of the call we have a clear picture of the build needed, and a fixed quote follows in writing within a couple of business days.
What Happens Between Build and Handoff
Most of the build phase is invisible to you, which is intentional. The workbook structure, form mappings, validation rules, and dashboard plumbing get assembled against the scope from discovery, and progress check-ins happen on a cadence that makes sense for the project size — usually weekly for small builds, twice weekly for larger ones. You see a working draft early enough that adjustments are easy and late enough that the structure is real. Final delivery includes the workbook itself, the form connection setup, a short reference document, and a live walkthrough of how to use and adjust the file after handoff. There is no portal to log into and no account that holds the deliverable hostage — the file is yours.
Ready To Talk Through Your Workflow?
Local Data Works is a Detroit, Michigan-based U.S. small business preparing to launch custom workbook builds. Join the waitlist for an invitation when discovery slots open, or get in touch about future availability.
Local Data Works is currently preparing for launch. Availability, onboarding, demos, and custom software services may be limited until final business, legal, and product setup is complete.
How It Works FAQs
How long does a typical build take?
Most single-form workbook builds finish in two to four weeks from kickoff. Multi-form workbooks with dashboards, validation, and ongoing intake usually finish in four to eight weeks. The exact timeline is part of the written scope so there are no surprises mid-project.
Do I need to send my data before kickoff?
No, but a sample form and a sample of the current workbook help. Real examples of the data — even a few anonymized rows — make it possible to mirror your real column layout, validation rules, and dashboard logic from the very first build session.
Where does the workbook live during the build?
The workbook lives as a local Excel file on hardware you control. We share working drafts directly with you for review, and the final file is delivered to your machine or shared drive. There is no third-party platform that holds the workbook hostage.
What happens if I want to change the workbook later?
Small changes — adding a column, renaming a tab, adjusting a dashboard formula — are usually a short session. Larger changes can be scoped as a follow-up project. Because the workbook is a normal Excel file, you can also make many adjustments yourself if you prefer.
Do you sign an NDA before reviewing my data?
Yes. If your workflow involves sensitive tenant, financial, or business data, an NDA can be signed before the discovery call. Local Data Works is a U.S.-based small business and treats client data with the same confidentiality you would expect from any professional services firm.
What does the optional ongoing retainer typically include?
Small adjustments — adding a column, adjusting a formula, mapping a new form, tweaking a dashboard — handled within a defined response time. Some clients use a few hours per quarter; others need monthly check-ins as their operations grow. The retainer is sized to the actual workload.
Can I bring my own existing workbook into the build?
Yes, and many clients do. The build often starts by reviewing a workbook the business already uses, keeping the structure that works, and rebuilding only the parts that drift or take too long to maintain. Your historical data carries through the build.
Related Pages
Local Data Works is a U.S.-based small business building custom spreadsheet software for landlords, property managers, and operators. Workbooks live as local files you own — no monthly platform fees and no migration away from the tools your team already uses.