Straight answers.

An NDA by default. We sign a non-disclosure agreement before you share any data or documents. If your firm has its own, we sign that instead.

Your data stays put during the build. We build and test on sample data, and touch your real records only inside your own systems or tools you approve. If a working copy is ever needed, it stays in storage you approve.

Access you control. You create our accounts in your systems with only the access the job needs, and can switch them off at any time. We never ask for your passwords; ours sit in a password manager behind two-factor sign-in, and the keys a build needs are kept in your accounts’ settings, never in code.

No subcontractors. The person on your intro call does the work. If a project ever needs another specialist, we ask you in writing first, and they sign the same NDA.

AI only with your approval. Nothing of yours goes to an AI model without your written approval. When you approve it, we use commercial AI services whose terms say they do not train on what they are sent, never consumer chat tools. Without it, we build the workflow without the AI step.

Yours, and cleaned up at the end. You own everything we build. When we finish, we remove our access, delete any working copies and confirm it in writing.

Assessment exports stay under your control. Assessment exports stay in a folder in your own account, or in encrypted storage you approve in writing, and are deleted within 30 days after the walkthrough.

Google Workspace, including Google Meet: our email, calendar, documents and video calls.

GitHub: code and documentation, not client records.

The tools a build runs on sit in your own accounts, under your own contracts with those providers. Streamlit Community Cloud hosts only our public demos and never holds client data.

Law firms: we work under a confidentiality agreement and follow your written instructions, which supports your own duties to protect client information and supervise outside providers. Those duties stay yours, and we do not advise on them.

Accounting firms: we use tax-return information only to perform your engagement, on your written instructions, and only as section 7216 of the Internal Revenue Code and the FTC Safeguards Rule allow. Whether a disclosure to us needs client consent is your firm’s decision.

Nothing confidential goes into an AI tool unless you approve that specific use in writing.

Yes, by default. We sign a non-disclosure agreement before you share any data or documents, usually before the assessment starts. If your firm has its own NDA, we sign that instead.

No. That is the normal starting point. Spreadsheets that disagree, missing fields and numbers spread across tools are all fine, so you do not need to tidy anything first.

The assessment finds where the gaps are, what the data can already support, and which fixes are worth making. Cleaning is part of every build.

None to start. We work with what you already use, such as QuickBooks, Clio, Salesforce, Shopify, Gmail or Outlook, and Slack or Teams.

Dashboards are built in Streamlit, Power BI or Tableau, whichever suits your team. If a workflow needs a new tool, it is set up in an account you own.

Software licences, hosting and AI usage are billed to you directly by each provider. We do not resell or mark up any of them.

Clio and QuickBooks are trademarks of their owners. Rada AI Consulting is not affiliated with or endorsed by them.

It reads. It sorts incoming emails and documents, pulls details out of them into a fixed form, summarizes a week of activity, or drafts a reply for a person to check.

It does not make decisions. Fixed rules decide where things go, every value the AI records is checked against the original text, and anything unclear goes to a person with the reason. You can watch this happen in the inbox demo.

For work that only moves data between systems, a plain automation is cheaper and more reliable, and we will tell you which is which before you pay for either.

You do. Dashboards, workflows, code and documentation are handed over as yours, and they run in your own accounts, so there is nothing to migrate if we stop working together.

Your team runs it. You get a walkthrough and written documentation, and someone on your side who knows how it works. Everything stays in your own accounts, and we remove our access and confirm it in writing.

Automation builds include 60 days of fixes for anything that does not work as described in the written scope. Changes, new features, or breakage caused by updates to other apps after launch are covered by monthly care or agreed separately.

Every automation is built with error handling, so a failure is flagged instead of silently skipped. Automation builds include 60 days of fixes after launch.

After that, a monthly care plan keeps an eye on it, for a fixed monthly fee, month to month. You also get documentation, so anyone on your team can see how it works.

The intro call is free. We suggest starting with the Quick-Start Data & Automation Assessment: a fixed $2,500, two weeks. It covers your data and your workflows. You get a review of up to three data sources and three workflows or tools, what your KPIs can and cannot show, a ranked list of automation opportunities, a build-or-buy recommendation, three prioritized next steps and a 60-minute walkthrough.

The Quick-Start Data & Automation Assessment looks at your business data and workflows. It is not a financial-statement audit or review, or any other attest or assurance engagement.

Prices exclude sales tax where it applies. Payment terms are set out in your written scope.

The assessment takes two weeks. A build after it, such as a dashboard, an analysis or an automated workflow, typically takes one to five weeks. Timelines start once we have access to your data or apps, assume feedback from you within two business days, and are confirmed in the written scope before work starts.

You will need someone who knows how the business runs and can spare an hour or two a week. No technical staff needed.

Yes. E-commerce shops and other small businesses have the same problem in different worlds: orders, refunds, support tickets and numbers spread across tools. If your week has repetitive paperwork in it, it is worth a call.