From the first email to the morning check
Seven steps. Each one says what we do, what we need from you and how long it usually takes. A typical integration runs four to eight weeks from scoping call to go-live.
-
01
Read your first email
1 business day
What we do
Reply within one business day with a short list of questions and two or three times for a scoping call.
What we need from you
Which platforms you use, the step someone does by hand today, and any date you have to hit.
-
02
Map how the data moves today
1–2 weeks to schedule and finish
What we do
A 60–90 minute scoping session. In Monterey County we can do it at the winery with the tasting room and office staff; elsewhere in California, over video. We watch the manual steps and note every field that gets copied.
What we need from you
Admin or read-only access to each system, a sample month-end export, your chart of accounts and 30 minutes from your accountant.
-
03
Quote a fixed price in writing
Within 5 business days of the session
What we do
Send a written scope: what the integration does, what it doesn't, deliverables, timeline, price and payment milestones.
What we need from you
Questions, changes and a signature when it's right.
-
04
Build against a sandbox
Most of the project, 2–5 weeks
What we do
Write the code against sandbox or test accounts, never your live books. For accounting work we use a QuickBooks Online or Xero test company. We share progress weekly.
What we need from you
Sandbox access, and quick answers when a mapping question comes up.
-
05
Run it in parallel and reconcile
1–2 weeks
What we do
Run the integration on real data for a set period while your staff keeps doing it by hand, then compare the totals for each account and each location. Migrations get a full trial push and an error report.
What we need from you
One person to compare results and sign off on the checklist.
-
06
Switch it on
1 day, plus a delta push for migrations
What we do
Deploy to your Google Cloud project, turn on the schedule and alerts, and watch the first live runs closely.
What we need from you
A go-live date that avoids a club batch day or a release weekend.
-
07
Hand over and keep watching
30-day warranty, then month to month
What we do
Hand over the repository, field mapping and runbook. Anything that doesn't match the signed scope in the first 30 days is fixed at no charge. After that you can move to a monitoring plan or keep the code and run it yourself.
What we need from you
Decide whether you want monthly monitoring.
Avoid the four things that stall projects
-
API access that nobody turned on.
Some connections, such as Tock's full order sync with Commerce7, have to be enabled by the vendor. We send the requests in week one so they don't block week four.
-
Renaming clubs or tags mid-migration.
Commerce7's guide warns against changing club names, customer tags or departments before the final push. Freeze them once mapping is signed.
-
Turning on apps that copy data too early.
Klaviyo, Mailchimp, loyalty and shipping apps can create duplicates if they connect before the migration finishes. Wait for our go-ahead.
-
A chart of accounts still being reworked.
If your accountant is restructuring accounts or locations, we wait for the final list before writing the mapping.
Step one is an email.
Request a scoping call