Oakas ← Back to the site

Frequently Asked Questions

Straight answers, plainly.

Everything people usually want to know before booking a call. If your question isn’t here, support@oakas.ai reaches a human.

What does OAKAS actually do?

We’re an AI consulting firm for small and medium businesses. We find where your team loses hours to recurring manual work: leads answered late, invoices chased by hand, the same report rebuilt every Monday. Then we design and build the custom AI systems that take that work over.

What does it cost?

Every build is fixed-scope and priced before work starts. You know the number before we write a line of code. No hourly meters, no surprises at the end. After launch, most clients keep us on a monthly retainer for hosting, maintenance, and improvements.

Who owns what you build?

You do. All of it. Source code, data, accounts and keys are handed over in full, engineered and documented to run without us. If you’d rather we keep hosting and maintaining it, we can, for a simple monthly fee. Your call.

We’re not a technical company. Is that a problem?

No. Most of our clients aren’t. You describe the work in plain language; we translate it into a system. Hand-off includes training your team, and the systems are built to be used by the people who run the business, not by engineers.

Do we have to replace the tools we already use?

No. We build around what already works: your calendar, your accounting software, your phone system. Where a rented subscription isn’t earning its keep, we’ll tell you, and many clients end up folding several subscriptions into one system they own outright. But nothing gets ripped out for the sake of it.

How long does a build take?

The timeline is scoped with the price, before work starts. We deliberately scope the smallest system that moves the needle first, and you see working software early and often. We don’t disappear for a quarter and return with a slide deck.

What happens on the discovery call?

Thirty minutes, free, with the person who scopes and builds every system, not a salesperson. You tell us where the hours go; we tell you plainly whether AI can bring them back, and what the smallest first build would be. If the honest answer is that you don’t need us, we’ll say so.

What happens after hand-off?

The system is yours and runs without us. Most clients keep us on a monthly retainer for hosting, maintenance, and continued improvements; others take it fully in-house. Either way, you’re never locked in. The code and documentation are built so any competent engineer could pick it up.

Can a project qualify for the R&D tax credit?

Often, yes. Custom software development frequently meets the IRS’s four-part test for the federal research credit, and what you pay an outside firm to build on your behalf can generally count as contract research, provided you keep the rights and bear the risk, which is how our engagements are structured. We document every build (scope, iterations, broken-out invoices) so your CPA has what they need to evaluate a claim. We’re engineers, not accountants. This isn’t tax advice. Read the plain-English overview on our R&D tax credits page, then talk to your CPA.

Is our data safe?

Your systems run on your accounts and your keys, not ours. Your customer data stays yours, and we don’t reuse it, resell it, or train anything on it. When an engagement ends, our access ends with it.

Still Curious?

The discovery call is the fastest way to a real answer about your business.

Book a Discovery Call