01
Find the account history
Locate the records scattered across the tools your team uses.
AI workflow assistants · Edmonton + remote
AI assistants that work with your business systems.
I can build an assistant that finds relevant information, prepares work, and proposes actions inside the tools your team uses. Start with one workflow, with clear permissions and approval before anything changes.
Work directly with Brad Conklin, an independent software developer based in Edmonton.
Start with a free fit review.
If I can’t give you a fixed quote yet, the first paid phase is capped at $500 USD.
Pricing and process →
A job beyond the answer
The answer is only part of the job.
An assistant becomes useful when it helps complete a defined piece of work, using information your team can check.
02
Prepare the next piece of work
Assemble an account summary, draft a document, or prepare a follow-up.
03
Carry the decision into the system
Propose the update and show it to the person who needs to approve it.
Find the quotes. Prepare the follow-up. Ask before acting.
The assistant would show which records informed its draft and what it proposes to change. A person reviews the action before the system carries it out.
Illustrative example
01 / Request
Find the quotes needing a follow-up.
Prepare a follow-up for Example Customer and propose the next-contact date.
02 / Retrieved records
Show the source information
Q-104 — awaiting customer response.
Q-108 — additional information requested.Sources: quote records Q-104 and Q-108, within this staff role’s access.
03 / Proposed work
Draft + proposed update
Draft: “Following up on Q-104. Do you have any questions about the quote?”
Proposed change: set Q-104’s next-contact date to 18 September in this fictional example.
04 / Review
Awaiting approval
A person checks the source records, draft, and proposed date before any update.
No change yet05 / Approved example action
Update Q-104’s next-contact date
After approval, the agreed record update would run. A changed proposal requires a new approval.
Example: approved06 / Audit result
Record what happened
Example history: approved date update completed for Q-104; Q-108 unchanged. Draft prepared, no email sent.
Illustrated outcome
Permission denied
A record outside the user’s access is not retrieved or changed.
Update failed
Record the failure and hand it back for review. Do not report a completed action.
Give the assistant a specific job.
01
Retrieve internal information
Find relevant information with source references a person can check.
02
Assemble an account summary
Summarise the open jobs for one customer using the records that role may access.
03
Prepare a document or follow-up
Draft a quote follow-up or an onboarding checklist from approved material.
04
Propose a bounded record update
Show the exact change, such as a next-contact date, and ask for the agreed approval.
Access, data quality, and the interfaces available in your systems determine what is feasible.
Make the action visible before it happens.
01
Respect existing access
Scope information to the signed-in user’s access.
02
Show the proposed change
Make the action and the records it uses visible before it runs.
03
Require the agreed approval
Keep review tied to the actual proposed action.
04
Record outcomes and failures
If a source is missing, a request exceeds permission, or an update fails, provide a clear hand-off.
A fixed reminder schedule belongs in ordinary automation. An assistant is useful when someone needs to ask, interpret, and review.
How projects start
Start with one request and one approved action.
Start with a free fit review. If the requirements are clear enough, I provide a fixed quote directly. If important questions need investigation first, I’ll propose a small planning phase with an agreed scope and price of no more than $500 USD.
Choose a specific task
Describe a request your team would make and the information needed to answer it.
Agree on one useful version
Start with one staff role, one data source, one request, and one proposed action.
Check the result and its boundaries
Review source accuracy, permissions, approval, failed actions, and the costs of running the assistant.
You keep the documented requirements, findings, recommended approach, scope boundaries, and acceptance criteria. When the build is viable and sufficiently defined, the handoff includes a fixed proposal for the first implementation, with timing and operating responsibilities. If the right answer is not to proceed, you receive the reasons and alternatives instead. You can use the handoff with Featherply, another developer, or nobody.
Start a conversation
What would you ask the assistant to do?
I’ll review your message and reply within two business days with any initial questions and a suggested next step. This initial fit review is free.
No paid work starts until its scope and price are agreed and you explicitly approve it.
Privacy and your enquiry
I treat what you share as private and use it only to review your enquiry unless we agree to use it for a project. Share only what you are comfortable sending; a short description or anonymized example is enough to start.
This page may use MaxMind to estimate your country or province from your IP address and adjust its wording. We don’t request precise device location or attach the inferred location to your enquiry. Campaign links can select regional wording independently of your location.