Foxy Fox Labs logoFoxy Fox Labs
Email me Book a free call

Frequently Asked Questions

The short version of how Foxy Fox Labs works. Anything else, just ask.

How do you handle my data and system access?

We follow least-privilege access, every time: we only ever ask for exactly what the project needs — read-only if we're only reading, one specific write permission if we're writing, never broad admin access "just in case." Access is set up under your own accounts (a dedicated user, role, or connected app), never your personal login. Once the project is delivered, we don't keep any working access — you rotate the keys at handoff, and that's it.

What happens if the automation breaks later? Do you offer ongoing support?

Every project comes with 30 days of warranty coverage: if something breaks while doing the job described in your proposal, we fix it free. (New feature requests aren't covered under warranty — those are a new quote.) After the warranty period, we offer an optional care plan — monthly monitoring and small tweaks, or fixes quoted as they come up — starting at $75–$150 per month, for projects where ongoing peace of mind is worth it.

Do I own what you build?

Yes. Once the project is paid in full, you own the custom code and configuration outright, and you're free to use, modify, or extend it with any developer or technical resource you choose — you're never locked into Foxy Fox Labs. We may reuse general-purpose techniques and know-how on other projects, but never your confidential data or your specific business logic.

Which tools and systems do you work with?

So far, I've worked with Google Cloud, BrightPearl, Vertafore AMS360, and BigQuery. I haven't worked with other platforms yet, but I'm confident I can pick up a new system quickly. If it has an API, an export feature, or even just a file you can download, it's usually workable.

How long does a typical project take?

It depends on the project's complexity — anywhere from same-day for a simple settings fix, up to several weeks for a project connecting multiple systems. You'll get a specific estimate with your quote. The clock starts once your deposit is in and we have access or sample data in hand, and if anything changes that estimate, we flag it within the first couple of business days rather than letting a deadline quietly slip.

What if my process is messy or undocumented?

That's normal — most small-business processes live in someone's head, not a manual. Part of the free audit call or discovery process is walking through exactly how the task is handled today, step by step, so we're building around how things actually work rather than how they're supposed to work. Messy doesn't disqualify a project; it's just something we sort out before quoting, not after.

How do payments work (deposit, milestones)?

It depends on project size. Smaller, simpler projects are typically 50% deposit to begin and 50% on delivery. Larger projects involving more complex system integrations start with a discovery fee (fully credited toward the project if you move forward within 30 days), followed by a staged payment plan tied to real checkpoints — kickoff, a successful end-to-end test, and delivery — rather than one lump sum. The exact structure is always spelled out in your proposal before anything begins.

If a vendor charges its own access or subscription fees, those are billed to you directly by the vendor. They're never part of our price.

Still have a question?

Bring me the task your team groans about every week. In 30 minutes we'll know whether it can run itself.