Mycel Deployed Partnership

A year of progress.
Built with your team.

Four total workflows per year, with an agreed roadmap and one primary active build. A continuing relationship for useful implementation, adoption and improvement.

The rhythm of the year

Four priorities. Steady progress.

Four workflows, connected by one continuing roadmap. Build one priority at a time, then use what the team learns to shape the next.

First workflowTargeted within 60 days
Second workflowNext quarter
Third workflowFollowing quarter
Fourth workflowFinal quarter

The first-workflow target depends on agreed scope, access and client dependencies; one workflow follows in each remaining quarter. One primary build is active at a time.

Choose the fit

Same four-workflow commitment.
Different scope and reach.

Foundation

$30,000annual fee

Workflow portfolio
4 contained, single-team workflows
Business reach
One function
Roadmap reviews
Quarterly
Upkeep + small changes
2 hours / month per account

Growth

$45,000annual fee

Workflow portfolio
4 priorities; example mix: 2 contained + 2 connected
Business reach
Up to two teams
Roadmap reviews
Monthly
Upkeep + small changes
3 hours / month per account

Scale

$60,000annual fee

Workflow portfolio
4 priorities; potentially all connected only if scope estimates fit
Business reach
Up to two functions
Roadmap reviews
Monthly
Upkeep + small changes
4 hours / month per account
Contained or connected?
  • Contained: One owner, one team, standard software connections and bounded rules.
  • Connected: Documented connections, multiple stages, approved system updates, exception handling and a manual fallback.
What every workflow includes
  • Plan and test: Process map or diagram, acceptance criteria and test set.
  • Release and operate: Accepted production release and operating guide.
  • Learn and hand off: One training session and handoff; recording only with client permission.

Upkeep allowances cover the entire scoped portfolio per account, not each workflow. The accepted scope defines what they cover.

Beyond the builds

Keep the work useful.

A continuing roadmap

A prioritized roadmap and action list, informed by business needs and adoption.

Measures with an owner

A named owner, baseline and updates for the agreed performance measure. Review use, issues and the time spent checking and correcting outputs.

A refreshed handoff

A refreshed year-end handoff pack, with tier upkeep throughout the year.

Time saved is capacity, not automatically profit. We agree what to measure and review the evidence, including exceptions and running costs.

A clear agreement

Know what is included.

What the written scope makes clear
  • Workflow: A repeatable process: owner, trigger, inputs, output and acceptance criteria.
  • Agreed boundaries: Systems, data, users, owner and approver; tests and AI quality thresholds; exceptions, manual fallback, acceptance and rework procedure.
  • Apps and interfaces: No custom app or interface by default in annual tiers; complex work needs a custom quote.
  • Canon: A shared process and decision-rule record, only if named in accepted implementation scope.
  • Changes: New features, integrations, departments, security requirements, volume or major vendor changes require written rescoping.
  • Separate costs: Licenses, software-connection usage, hosting and other third-party costs are additional to Mycel fees.
  • Agreement: Defines ownership, accounts, deliverables, reusable IP, exports, source/configuration and exit rights.
  • Hosting and sensitive data: Managed hosting and sensitive or regulated data require explicit responsibilities, review and authorization.
  • Proposal: Confirms payment, cancellation, coverage hours and unused-time treatment.
See assessment and proposal

Start a conversation

What keeps landing back on your desk?

Bring one recurring task. Let’s talk through a sensible first step.

Book a free 30-minute discovery call
Mycel Group / Meet the founders

Meet Austin & Evan.

At Mycel Group, we bring operating judgment, thoughtful engineering and support for adoption together. We build around the people doing the work.

Austin Barnhart

Founder, Mycel Group

Austin Barnhart

I bring an operator’s perspective to AI. The work comes first; the technology serves it.

Read Austin’s full biography

Operating background

Start with the business.

My background is corporate consulting and operational performance, with a focus on leadership, profitability and the mechanics of how work actually gets done. That experience shapes every question I bring to AI: What is the business trying to improve? Where does the work stall? What would let the team move with more speed and more confidence?

Hands-on with AI

Learn by building.

I’ve spent years working with these tools directly: organizational models, operating dashboards, executive agents and assistants, documentation systems, and the workflows that connect them. That practice is where the judgment comes from. It’s how I know where the tools are reliable, where they need structure, and what it takes to turn a capable model into a dependable part of a business.

How I work

Clarify the business. Then build the workflow.

I work with several leading AI platforms, and the choice follows the work: your purpose, existing systems, budget and information needs.

During assessment, we collect the operating knowledge that informs the proposal. If included in the accepted proposal, we develop and maintain your business canon as part of implementation, with your approval.

From that reference we build task-specific instructions and templates, test them against real examples, and refine together, keeping human judgment at the points where it matters.

Ownership and access are set out in the accepted agreement. Third-party software remains subject to its licenses and ongoing subscriptions. Documentation and training support continued operation; reliability also depends on your systems, access and upkeep. Support and changes follow the agreed scope.

Evan Persson

Technical Co-Founder, Mycel Group

Evan Persson

More than eight years of software engineering and architecture experience, connecting technical decisions to the way a business actually works.

Read Evan’s full biography

I’m Evan Persson, technical co-founder of Mycel Group. I bring more than eight years of software engineering and architecture experience to practical AI implementation, connecting technical decisions to the way a business actually works.

My background spans APIs, data pipelines, secure integrations, and cloud services. I’ve led engineers and owned systems from architecture through deployment and production support. That experience shapes how I approach implementation: reliability matters, ownership needs to be clear, and the work does not end when a system goes live.

At Mycel Group, we bring operating judgment and technical expertise together. We begin with the work a client wants to improve, then establish the information sources, access requirements, connections, and human review points needed to support it. From there, we configure suitable tools, connect them with existing systems, and test against real examples.

As lead developer and software architect for an AI voice-analysis project, I designed a pipeline that converted voice streams into text for language analysis. That work reinforced an important lesson: an AI model is only one part of a useful system. How information moves, how services connect, and how results are checked deserve just as much attention.

I believe clients should understand what we build with them. I document how each setup works, where its limits are, and what the team needs to know to operate it. Accounts, ownership and access are set out in the agreement.

My focus is practical: thoughtful engineering, clear documentation, and AI implementations that fit the people and processes they are meant to serve.

Have a task that keeps coming back?

Book a free 30-minute discovery call