Set Your Imagination On Fire.
Connect the tools you use.
Shape one useful job for an agent.
Shape your ideaChat it through. Leave with a starting brief.What would help?

Your agent
Meeting preparationPROPOSED WORKFLOWSelections plan a workflow, not permissions.
Prewritten examples, not live AI. Choices stay in this browser. No sign-in happens here.
A request. A working draft.
A person makes the call.
This site is our own example: an agent built it, and we decided what went live.
Inspect the example →Start with the job.
Then choose the build.
Start with what you want to make possible. We can build software, websites and connected systems, with AI where it fits. The first conversation helps us choose where to begin.
Talk through an idea, bring your notes and turn context into the next draft, brief or piece of research.
Help people find answers in approved business information, with sources they can inspect and a clear place for unanswered questions.
Quoting tools, dashboards, client portals, websites and integrations built around your work and the systems your team already uses.
Not sure where your idea fits?
The brief builder helps you name one first job, the material it needs and a decision for a person. You can keep it without contacting us.
An agent that starts
with your context.
Talk through an idea, bring your notes and turn context into the next draft, brief or piece of research.
Where it fits.
You want an agent shaped around your work rather than a fresh explanation every time you open a chat.
What we start with
- One recurring job and a representative example.
- Documents and notes you are permitted to use.
- The tools you want to connect, subject to access checks.
Personal AI Agents
Before a meeting, prepare a brief from the agenda and approved notes. Show unresolved questions and the source material so you can check the result.
You check the draft, correct the context and decide what happens next. Any sending or system changes need an agreed approval design.
Define the test
before the build.
Can you trace the key facts to the source notes? Does the brief distinguish known facts from unanswered questions?
What a scoped build includes
A first workflow, a map of its inputs and decisions, representative test cases and a handover plan. The proposal sets the deliverables and support boundary.
What needs discovery
Access rights, source quality, provider costs, integration limits and the effort required. No platform access or delivery schedule is assumed by this brief.
Put shared knowledge
within reach.
Help people find answers in approved business information, with sources they can inspect and a clear place for unanswered questions.
Where it fits.
Your team uses the same policies, project notes or operating documents and needs a consistent way to find and check information.
What we start with
- A small, approved set of current documents.
- Who can access each source and who maintains it.
- Real questions, including ones the material cannot answer.
AI for your team
A colleague asks how to prepare a project handoff. The proposed tool returns the relevant checklist and identifies the document version used.
A document owner checks sources and access. The build should surface missing or conflicting information instead of filling gaps with guesses.
Define the test
before the build.
Does each answer point to an accessible source? Does the tool stop and flag an unsupported question? Do access tests match the agreed roles?
What a scoped build includes
A first workflow, a map of its inputs and decisions, representative test cases and a handover plan. The proposal sets the deliverables and support boundary.
What needs discovery
Access rights, source quality, provider costs, integration limits and the effort required. No platform access or delivery schedule is assumed by this brief.
Build the thing
your idea needs.
Quoting tools, dashboards, client portals, websites and integrations built around your work and the systems your team already uses.
Where it fits.
You have a workflow that needs its own interface, data model or connection between tools, beyond a single chat experience.
What we start with
- A walkthrough of the current process.
- Sample records with private information removed.
- Required systems, API access and the person making each decision.
Custom Software
An inquiry moves into a review queue with the right context. A person checks the proposed next step before the workflow continues.
Agree what is automatic, what needs review and how failures are recovered. Test those paths before moving real data or publishing changes.
Define the test
before the build.
Can a representative user complete the job? Are duplicates, missing data, permissions and failed connections handled visibly?
What a scoped build includes
A first workflow, a map of its inputs and decisions, representative test cases and a handover plan. The proposal sets the deliverables and support boundary.
What needs discovery
Access rights, source quality, provider costs, integration limits and the effort required. No platform access or delivery schedule is assumed by this brief.
The inputs matter.
So does the decision.
Pick a situation to see the information, draft and human review in a possible workflow.
ILLUSTRATIVE · PREWRITTEN EXAMPLES · NO ACCOUNTS CONNECTED
One job.
A clear way to test it.
Map the situation.
Walk through one real example. Find the source material, who needs the result and what should stay manual.
Agree the boundaries.
Agree the scope, price, access, provider costs and acceptance test before the build begins. The proposal also sets out training and monthly support.
Build, test and support.
Review progress and test real examples, including missing information and errors. After approval, we help your team get started and provide ongoing support within the agreed scope.
This draft is
the working example.
We started from an existing Minds On Fire homepage draft and the owner's request for a complete site with more room at the edges. The agent assembled the pages and local interactions for review.
The example below recreates that internal design workflow. It includes no client identity, client data or measured customer outcome.
Source: our own website build, recreated and redacted.
What changed, and who decides
Try the actual output rather than a simulated video.
Use the working brief builder →Imagination, with
something to show for it.
Minds On Fire builds AI agents and software around the way people work. We start with a specific ambition and make the next step tangible.
Built around
your context.
Your documents, your ways of working and your judgement matter more than a long feature list. We use those to shape the first job and the test that tells us whether it works.
Our own agent assists with documents, campaigns and website drafts. This site is one of those examples: our own work, not a client deployment.
See how it was built →- Since
- 2017
- Based in
- Woodstock, Ontario
- Serving
- Canada and the United States
- Partner role
- Design and hosting partner for We Are One Tour events.
Begin with a conversation.
Build around a clear first job.
We work out the fit, access requirements and scope before proposing a build. The right answer may be an agent, a team tool, a custom application or a simpler change to what you already use.
What happens
from here?
Do I need a finished plan?
No. A goal, a problem or an unfinished idea is enough. Start with one thing you want to make possible.
Can we begin with one part?
Yes. A single job gives us something specific to test before expanding the build.
Is the brief builder using AI?
No. The brief builder combines your answers with predefined suggestions. It provides a starting structure, not validated scope, a quote or a feasibility assessment.
Can you connect the tools we already use?
We review the tools, available APIs, account plans and permissions first. The examples here do not establish that a connection is available or configured for your accounts.
Who decides what gets sent or changed?
We agree the review and approval paths for each build. The workflow examples show where a person decides; the exact technical controls need to be designed and tested for that scope.
What does a build cost?
The scope depends on the first job, connections, access needs and ongoing support. We discuss those before preparing a proposal, including any separate provider costs.
What happens to my answers here?
They stay in this browser until you copy, download or choose to share them through your email app. Clear the saved draft with the control in the idea builder.
What happens after we talk?
We define the first job, required material, review decisions and acceptance test. A scoped proposal comes before a build commitment.
Tell us what you
want to make possible.
You can start a conversation without using the idea builder. If you have a brief, include it so we have something concrete to discuss.
Your next step.
Request a conversation by email. Share the job you have in mind, who it is for and a few times that work for you.
Opens your email app with a draft. You review and send it there. This page does not send email or confirm a booking.
Prefer a calendar? Choose a time ↗
Opens the existing Minds On Fire calendar on Calendly. Your brief is not transferred. Copy it if you want to bring it to the conversation.
Woodstock, Ontario
Serving Canada and the United States
No finished plan needed.
A sentence is enough. The idea builder can help you turn it into a first job, a list of inputs and a review decision.
If your email app does not open, copy the address above and paste your brief into a new message.
Make your starting brief.
Three small steps. Keep the result before sharing any contact details.
Your information
stays with you.
This note covers the idea builder on this page. Our full privacy policy covers everything else.
What stays in your browser
The idea builder stores your goal, audience, optional context and current step in local storage on this device. The app canvas also stores the selected situation, app names and optional custom connector request. No authentication tokens are stored or requested. No account is created. The idea builder makes no remote AI calls. Fonts and images are embedded.
You choose what leaves
Copying places the brief on your clipboard. Downloading saves a text file. Email actions open your email application with the brief included; that application and your email provider handle the draft and any message you choose to send. Nothing is submitted to Minds On Fire by this page. The optional calendar link opens Calendly, a separate service with its own privacy notice and cookies. This page does not pass your brief to Calendly.
Clear your draft
Use “Clear draft on this device” in the idea builder to remove its saved answers. Use “Start over” on the canvas to clear both the brief and your app selections and custom request. An empty canvas preference remains so a reload stays empty. Copies, downloads and email drafts you create must be deleted separately. Local storage can be unavailable or cleared by your browser. Avoid entering confidential, personal or regulated information.
Before a public launch
The final policy must describe the actual hosting, forms, retention, service providers and contact process. Any future analytics should record journey events without collecting free text from your brief.
Return to the idea builder →A starting point,
not a scoped offer.
The brief builder uses predefined suggestions and your inputs; it does not call an AI model, assess feasibility, validate an integration or generate a quote.
Examples and scope
Workflow examples are illustrative. Actual tools, permissions, review controls, provider costs, delivery and support would be agreed in a separate proposal and agreement.
No submission or booking
Email links prepare drafts in your email app. You decide whether to send. A conversation is not booked by using this page.
Full terms
These notes explain the idea builder. Our full terms and conditions apply to the website, and any work is agreed in a separate proposal and agreement.
Talk to us →