Automation FAQ — Questions about automating your business.

It depends on the process: how many systems it touches, how messy the inputs are, and how many exceptions it has. Describe yours to the agent and it will give you a directional range in about a minute. Every project gets a fixed quote before any work starts.

Yes. A 15-minute intro or a 30-minute call with the founders, whichever suits you. No obligation to buy the audit or build anything.

We map one process end to end, measure how long it takes today, and give you a written recommendation of what to automate, how, and roughly what it costs. If the audit can't find what to automate in your business, and how, we refund the $199.

Every build gets a fixed quote before any work starts. It depends on how many systems the process touches, how messy the inputs are and how many exceptions it has. If you do the audit, its ranked opportunity list includes estimated hours and a fixed-price build range for each process.

No. The audit comes with no platform commitment and no obligation to build. You can stop after the free call, after the audit, or after any build.

Request it on the contact page. We confirm the details by email and send you a payment link.

Just one process that takes too much of your team's time. Tell us how it runs today, and you'll leave with a clear view of whether it's worth automating, even if the answer is no.

Most single-process automations take one to three days to build, plus testing with your team before anything goes live. The exact timeline is agreed before work starts.

Four things: someone who does the work day to day for a walkthrough, a process owner who can make decisions and approve the automation, appropriate access to the tools involved (ideally a test environment or limited-permission accounts), and real examples such as historical emails or documents to test against.

Yes, and we recommend it. We automate one process, prove the result against a baseline, and only then suggest the next one.

We measure how long the process takes before we build anything. After launch we compare against that baseline, so the time saved is something you can see rather than something you're told.

Every run is logged, failures alert a person, and exceptions are routed for review instead of silently skipped. If you want ongoing help, managed automation covers monitoring, maintenance, optimization and support.

The founders. The people you talk to are the people who build it: Fred leads client engagements and audits, Balash owns the engineering, and Julia owns pricing and contracts.

Usually not. We build around the systems you already use and pick technology per process. Where a new tool genuinely helps, we explain why and what it costs before recommending it.

We're platform-neutral and choose technology per process: workplace tools like Microsoft 365, Google Workspace, Slack and Teams; CRMs, project management and accounting systems; automation platforms like n8n and Make; language models from OpenAI, Anthropic (Claude) and Google (Gemini); and custom code through APIs and Python or JavaScript services.

No. Some problems need AI, some need a workflow, an API or a few lines of code. Language models are useful for reading and interpreting unstructured input; for everything else, simpler and more predictable tools usually work better. We use the simplest reliable solution.

You do. Workflows, code and documentation belong to you, and automations run in accounts you own, so you are never locked in to us.

Repetitive work that follows predictable rules: sorting and routing email, extracting data from PDFs and invoices, onboarding, keeping systems in sync, recurring reports, reconciliation, payment reminders and more. Decisions that need judgment stay with your people.

We use the least access a workflow needs, keep credentials in your accounts where possible, log what each automation does, and document everything so you can own it.

Only where a step needs it, and only the data that step needs. We use provider settings that keep your data out of model training where available.

No. Nothing goes live without your process owner's sign-off, and sensitive actions can always require a person's approval.

It stops guessing. Anything outside the defined rules is routed to a person for review, and failures trigger an alert.

That isn't the goal. We remove the repetitive steps around the work and leave decisions with your people. Exceptions are routed to a person, not guessed at.

Yes. We meet in person around the Sacramento region and work with teams anywhere in the U.S. by video.

Yes. We're happy to meet at your office in Roseville, Rocklin, Granite Bay, Folsom or Sacramento. Elsewhere, we meet by video.

We don't resell a platform and fit your process to it, automate decisions that should belong to a person, build something because it's technically interesting, or measure success by the number of workflows running.