Judgement before a build — whether an AI idea is real, whether it can be built, what it will cost, and where it will fail. Arc weighs the route before you spend on demos and tools.
WHAT IT ANSWERS
The judgement, before the spend.
The hardest part of an AI initiative is often deciding whether to begin it at all — most ideas demo before they are understood, and the cost of being wrong shows up months later, in production. A Feasibility Study answers the questions a demo cannot: is the value real, is the technical path real, and where does it break.
This is also where Arc's consulting and strategic R&D sit — judgement on a hard, uncertain technical question, from a house that builds. Arc advises, but as someone who has shipped the thing it is advising on, not as someone reading the field from outside.
THE FORMS
Three depths of judgement.
From a scoped study to sustained direction to research taken on — the deeper the question, the longer Arc stays with it.
Technical Feasibility
~2–4 weeksCan this be built? Where is the risk, and is the path real? A scoped study ending in a clear go / no-go.
Strategic Consulting
~2–4 monthsSustained direction on a hard, uncertain technical question — what to build and how, from a house that builds rather than only advises.
Strategic R&D
ongoingWhere the question needs research, not only advice. Arc advises it — or takes it on. When Arc builds it, that becomes forward-deployed engineering. → FDE
WHO IT'S FOR
- A founder weighing an AI product
- An enterprise weighing an internal AI initiative
- An investor or incubator judging a technical route
- A team with an idea, but no picture of the risk
THE SHAPE
How a study runs.
- 01
Intake
The idea, the constraints, the decision that has to be made — and what success would even mean.
- 02
Landscape
What already exists, what is proven, and what is still unproven at the frontier of the problem.
- 03
Risk mapping
Where the technical risk concentrates — the parts most likely to fail, and how expensive failure would be.
- 04
Architecture options
The viable routes to build it, each with its trade-offs in cost, risk, and time.
- 05
Build / buy / partner
What is worth building, what to source, and what to licence — and where Arc could carry it forward.
- 06
Recommendation
A clear go / no-go, with a prototype scope and an evaluation plan if it is go.
WHAT YOU GET
A decision you can defend.
- Feasibility report
- Technical risk map
- Architecture options
- Build / buy / partner recommendation
- Prototype scope
- Failure assumptions
- Evaluation plan
- Go / no-go recommendation
FEASIBILITY VS DIAGNOSTIC
Feasibility Study
Nothing is built yet. The question is whether to build — and what it would take.
Diagnostic
A system exists. The question is what is real in it, and what must be fixed before deployment. See the Diagnostic.
ENQUIRE
Bring the question.
Write to us with a concise account of what you are weighing — the idea, the constraint, the decision you need to make. ArcSoft Pty Ltd signs and holds the commercial terms.
A deeper engagement, or a bigger build? Forward-Deployed Engineering →