Advisory
We run this process at the strategy level while guiding others on execution.

Software development projects, especially data-intensive ones like machine learning, are highly uncertain: requirements and priorities change as more information becomes available. For this reason the field has adopted Agile software development methodologies as an industry best practice.
Discover and Design are the Blueprint.

Part of the Blueprint
Identify stakeholders, investigate issues, frame problems, understand use cases, gather requirements, interview business leaders and tactical and technical experts, research benchmarks and best practices.

Part of the Blueprint
Perform analysis of data, create wireframes and prototypes of possible solutions, and design mockups or interaction flows, and propose plans to get from the current state to the desired future state.

Scale the work from the Design phase into more ubiquitous and scalable solutions using realistic real-world components and production-ready systems. This is the fun part where code is written and dreams come to life.

Deploy solutions into production, operationalize, transfer competency to your internal team, and move into maintenance mode with or without the Acorn team. This is when we put your vision out into the world!
New clients can start with Advisory, Execution or a Blueprint. If you are ready to commit, begin directly with Advisory or Execution. If you are not ready yet, begin with a Blueprint.
We run this process at the strategy level while guiding others on execution.
We own the whole process end to end.
Our initial discovery engagement, for clients not yet ready to commit to more. It covers the Discover and Design phases. We interview your leaders and technical experts, then deliver:
A Blueprint with a proof of concept adds an interactive prototype built on synthetic or mock data.
After a Blueprint, we propose a menu of options. It may include an Advisory or Execution engagement, or other offers with concrete outcomes.
Acorn works with clients in iterative cycles, each referred to as a “Sprint” or “Sprint Cycle.” Part of our onboarding is to establish who will play what role in the partnership's success. Typical roles include:

Say so. We split it into smaller, separate projects that pay back faster, and you choose where to start.
If you have not started a major migration, it often helps to wait a few weeks. We map and protect your existing data first, so history is not lost, and then you can migrate. The worst is when we start work while things are happening behind the scenes, and suddenly key pieces of information are mysteriously disappearing.
No. The early projects are the first pieces of that larger system and fold into it.