Commonquestions.
Q & A
How we work, what it costs, and what you own.
If yours isn’t here, email hello@cirql.ai and we’ll add it.
- Q01
What is CIRQL?
CIRQL is a team of forward-deployed engineers for industrial operators. We embed with your team, find where time and money are getting lost, build the tools to fix it, and stay to maintain them. Based in Minnesota, US-based team.
- Q02
How do we work together?
Three ways, laid out on our work-with-us page: a structured assessment that maps where your hours go; fractional forward-deployed engineers who build and maintain, scoped from the assessment; and one-off projects when you already know the single thing you want automated. Most engagements start with the assessment and roll into the build.
- Q03
How much does CIRQL cost?
The assessment starts at $2,500, and what you pay for it credits toward any builds that follow. Fractional engineering and one-off projects are priced by scope, because what you need is not the same as what the company down the road needs. Book a call for specifics.
- Q04
How fast does CIRQL deliver?
Once we are embedded, most requests ship in days. Website updates take 1–3 days, new collateral 2–5 days, workflow automations 3–7 days, full integration builds 1–3 weeks, and custom tools from scratch 2–4 weeks. See how we work for the full process.
- Q05
What industries does CIRQL serve?
Industrial companies doing $5M–$100M in annual revenue with 10–200 employees: manufacturing, distribution, field service, and procurement and operations teams.
- Q06
How is CIRQL different from hiring an agency or freelancer?
Agencies scope projects, bill by the hour, and leave when the project ends. Freelancers are hard to manage and disappear. We embed with your team — on site, on your calls, shadowing operations — and we stay to keep finding and fixing problems. You own everything we build. No vendor lock-in.
- Q07
How is CIRQL different from Salesforce, HubSpot, or NetSuite?
Those are products. We are a team. Salesforce gives you a CRM your business has to adapt to; we build one that adapts to your business. HubSpot builds for SaaS companies; we build for industrial sales. NetSuite gives you an ERP that takes 6–12 months; we deploy operational tools in weeks. Off-the-shelf software forces your workflows into their system — we build tools that fit your workflows exactly.
- Q08
Does CIRQL work with my existing ERP or systems?
Yes. We don't replace your existing systems — we fill the gaps around them. We integrate with ERPs like SAP, Oracle, NetSuite, and Epicor; accounting tools like QuickBooks and Sage; CRMs like Salesforce and HubSpot; email platforms; warehouse management systems; and anything else you already run. The goal is to make everything work together, not to rip and replace.
- Q09
What if I only need one thing built?
That is exactly what one-off projects are for. If you already know the bottleneck — purchase-order entry, a vendor-sourcing workflow — we can build that one thing and hand it over, priced by scope, no assessment required.
- Q10
How do you handle data security and confidentiality?
Every engagement starts with an NDA. Your data stays on your infrastructure — we don't store client data on our systems or share anything between clients. Tools we build run on your servers or your cloud accounts, not ours. Code ownership is yours from day one.
- Q11
Do I own what CIRQL builds?
Yes. Everything we build is customized to your business and runs on your infrastructure. You own the tools, the data, and the code. If we ever part ways, you keep everything. No vendor lock-in, no proprietary platforms, no hostage situations.
- Q12
Where should a mid-size manufacturer start with AI?
Start with measured workflow friction — quotes, work orders, email handoffs, inventory data — not a company-wide AI transformation. The best ROI usually comes from automation and structured data on top of existing ERPs and CRMs, then retrieval-grounded tools for internal knowledge. Read the full guide: Where should a mid-size manufacturer start with AI?
- Q13
What are the highest-ROI AI and automation use cases for distributors?
Distributors typically see the fastest returns on order intake and exception handling, pricing and margin guardrails across branches, inventory visibility and alerting, and sales follow-up tied to CRM state. See AI for industrial distribution.
- Q14
Can we use AI with our ERP without replacing it?
Yes — and that should be the default. Treat the ERP as the system of record; layer workflow tools, integrations, and AI-assisted experiences that read and post through governed APIs. Rip-and-replace ERP projects are slow and risky. Read Using AI with your ERP (without replacing it).
- Q15
What is the difference between RAG and fine-tuning for internal industrial data?
Retrieval-augmented generation (RAG) answers questions by retrieving relevant chunks from your documents and policies, then generating text grounded in that context — good for specs, SOPs, and tribal knowledge that changes. Fine-tuning adjusts a model's weights for narrower goals; it is usually secondary after RAG, access control, and evaluation are in place. See RAG vs. fine-tuning for internal industrial data.
- Q16
How do we assess AI readiness before buying software or hiring a team?
Readiness combines leadership scope, system-of-record clarity, integration paths, data naming, governance, and change management — not a single maturity score. Quantify value by translating weekly hours into dollars before you commit; our assessment does exactly this. Or read the readiness guide.
- Q17
Where is the CIRQL team located?
CIRQL is a US-based team based in Minnesota — no offshore development, no outsourcing. We show up on site to embed, and we work with operators here and in neighbouring states. Learn more about the team.
- Q18
How do I get started with CIRQL?
Book a 30-minute discovery call. We'll learn about your operations and show you what we'd build first. Most teams start with the assessment, which credits toward the work that follows.
Still have questions?
Book a 30-minute call and we’ll answer everything — plus show you what we’d build first.