I help owner-led businesses and professional teams turn a concrete problem into a useful website, a focused tool or a clearer process. We start with the people doing the work, the tools you already have and what a useful result needs to do.
People reach your website but cannot work out what you do, whether it fits their need or how to ask about a project.
An inquiry or quote moves between email, a spreadsheet and someone's memory, with repeated re-entry along the way.
A recurring report or proposal starts with the same documents, but each draft has to be assembled again.
Staff search through policies, manuals or prior work and still need to check whether the answer is supported.
An AI tool looks promising, but no one has defined the cases it must handle or what happens when it is wrong.
A clearer form, a reusable template or a deterministic rule may solve the problem. AI becomes an option when the task warrants it and its outputs can be checked.
Three practical ways to engage.
Choose the work by the result you need. Website and ordinary business-tool projects are scoped directly; they do not need to be called AI pilots.
A website with a clear job
For a business that needs visitors to understand its offering and take an appropriate next step. We define the audience, the pages they need and the inquiry path before building.
You receive: an agreed page and navigation map; copy based on your approved facts; responsive implementation of the agreed pages; checks of links and the agreed inquiry flow; and source files with handoff notes.
Bring: the services you actually provide, approved business details and claims, existing site/content, usable brand assets, intended audience and a person who can approve the copy.
Decision: whether the pages explain the business accurately and let a visitor complete the agreed task. We define acceptance before implementation.
For one task with recognizable inputs and an output someone can check. Possible scopes include organizing an intake, preparing a repeatable report or reconciling two exported records.
You receive: a written task specification; an agreed working tool; checks against representative examples; and source, configuration and operating notes for the agreed handoff.
Bring: examples of the work, the current spreadsheet or process, permitted test data, known exceptions and a reviewer who can say whether the output is usable.
Decision: whether the tool handles the defined task and where manual review remains. System integrations, access controls and operational support are agreed separately where required.
When the problem spans people, documents and systems, start by understanding the handoffs. These are separate engagements, selected according to what is already known.
A half-day working session and Workflow Teardown Readout: where the friction sits and whether deeper diligence is warranted. It does not include a pilot specification, baseline or implementation estimate.
A Workflow Diligence Readout with the current process, risk/value ranking, one pilot specification, estimate and a build, narrow, defer or stop decision. The established schedule is three calendar weeks after kickoff and receipt of agreed source material. Building the pilot is separate.
A Verified Workflow Pilot for one agreed workflow, with acceptance and stop criteria, risk-based tests, run records, client-owned code and a readiness memo. A Diligence Sprint or equivalent specification supplies the scope; the pilot is not a production rollout.
Bring: the people who run the process, representative inputs/outputs, current tools, failure examples and the decision-maker. The useful outcome may be a simpler process or a decision not to automate.
Support for the questions around the build.
Review an AI tool or vendor
AI Technical Advisory produces an AI Decision Brief and Advisory Record around a defined adoption, vendor or governance question. Bring the proposal, operating constraints and consequences of error.
The AI workflow evaluation option can define representative cases, failure criteria, source/behavior checks and reproducible results for an existing candidate. It ends in a bounded recommendation with limitations, not a certification. A test harness or new pilot build is separately scoped when needed.
Find information and explain it clearly
A document-search pilot can link an answer to approved source passages for a person to check. Bring the documents you may use, questions users actually ask and examples of answers that should be withheld. Scope it through the existing workflow Pilot.
Technical Communications provides an Audience-Ready Communications Package for explaining a technical product or service: audience brief, message/evidence map, agreed materials and maintainable source files. It is not a general advertising campaign.
Specialist services are available when the underlying work fits. Biotech and technical product ventures may need R&D, scale-up or process modeling; an ordinary service business does not automatically need those engagements. Federal work requires an eligible technical R&D opportunity or recurring federal proposal process. See the funding and proposal scopes.
Bring the problem and the material behind it.
The intended visitor or user, the task they should complete and who will approve the result.
Your existing website, forms, templates or exported records, with examples of a good result and a failed handoff.
Approved facts and content, rights to use the supplied assets, and any professional or organizational restrictions.
The systems the work must fit, access constraints and who owns deployment or operation after handoff.
Representative test examples that can be used in the agreed environment. We establish data handling before exchanging sensitive records.
A small scope with a visible finish.
Define the useful result
Agree on the audience or workflow, the outputs, exclusions and acceptance criteria. Confirm whether an existing tool, a website, a simple rule or a model-assisted workflow fits.
Review the source and shape the work
Check the facts, sample inputs, permissions and dependencies. Resolve missing content or unclear process decisions before they become implementation assumptions.
Build and review the agreed slice
Review the pages or tool against representative tasks. For AI-assisted work, include failure cases, source checks and the points where a person must decide.
Hand over the result and remaining decisions
Provide the agreed files, checks and operating notes. Identify production, integration, security, hosting or support work still required before operational use.
A website or focused tool can be a standalone fixed-scope project. A workflow can begin with a Teardown, Diligence or an already agreed Pilot specification. Advisory can be a single review or a separately agreed monthly retainer; nothing auto-renews. How engagements are scoped →
Relevant work, with its limits in view.
Team use reported
Proposal assembly from existing material
Tools for finding prior work, assembling drafts and producing supporting material show a method for recurring business writing.
Business-impact metrics are not established. The case describes single-operator tools; production interfaces, review workflows and integrations remain separate work. It is not a measured outcome for a small-business client.
A document-retrieval implementation demonstrates source-linked answers and a way to check the evidence behind them.
Built and tested on a small, controlled document corpus. Those results do not establish reliability on your documents or across all business decisions.
What needs a separate scope or a different professional.
No guaranteed leads, sales, search rankings, cost savings or business outcomes.
Hosting, maintenance, ongoing content work, paid tools, e-commerce, production integrations and support are not bundled promises. Agree on responsibilities and any additional work before launch.
No autonomous legal, accounting, HR or other consequential professional advice. A tool may prepare information; the responsible professional reviews it.
No blanket security, privacy or accessibility certification. The scope defines the environment, checks and remaining approvals.
No open-ended business strategy or unattended automation without a defined task, failure handling and an accountable owner.
Start with your decision
What keeps getting in the way?
Tell me who needs the website or tool, the task you want to improve and what you already use. We can agree on the smallest useful scope, the outputs you will receive and how you will review them.