The most useful AI plugin work often begins with something unglamorous: a person explaining the same process for the tenth time. Perhaps every new enquiry needs the same checks. Perhaps different team members write follow-ups in very different ways. Before encoding any of that, we ask whether the process is sound and which parts really should be consistent.
Brownsmith Dynamics starts by collecting a small set of real tasks and the guidance people already use. We look for the decisions that require judgement, the facts that must be current, and the recurring steps that can be described clearly. If there is no shared approach yet, a plugin will not manufacture one. We work with the owner to define the useful version first.
For a skills-based package, we turn that approach into instructions the AI client can apply at the right moment. Supporting reference files can hold approved service details or examples. A starter prompt can help a new user try the workflow. We test it with incomplete requests and exceptions, because the first clean example rarely tells us whether the instructions are usable.
For planning, work starts at USD $25/hour and can cost $40/hour or more. Maintenance is usually about $200/month. We confirm the hours and scope before quoting.
What the plugin can and cannot know
Instructions provide context and method. They do not automatically connect to a calendar, customer database, or inbox. If the assistant needs current records, we discuss a separate integration, perhaps an MCP server, and define its access independently. That distinction is useful for both security and expectations: someone using a guidance-only plugin should know which information they need to supply themselves.
We also discuss maintenance. A service description changes; staff learn a better way to handle a request; a platform changes how it installs extensions. Somebody needs to own those facts and review them. A package that accurately describes last year's process can still produce confident but wrong guidance today. We include a sensible update path and keep the material narrow enough to review.
Publication is another decision. A private internal tool has different needs from a public listing. Platform requirements, client interfaces, and review processes vary. Preparing files does not mean a listing has been accepted, and plugin publication does not guarantee that it will be recommended by the host. We explain what is ready and what the destination still requires.
Our current Brownsmith business-improvement toolkit uses focused workflows to help with business diagnosis, process review, organic acquisition, and implementation planning. The package carries reusable guidance; it is separate from any MCP-backed connection. For the reasoning behind that split, see our MCP article for service businesses.
If you want to shape a plugin around a recurring job, explore our business-efficiency service. Send a short outline through WhatsApp or the contact page. A sample request and the current process notes are enough to start the discussion.