Website editing assistant
Prepares text, image and page updates from your instructions. Your team reviews changes before publication unless a specific low-risk action has been authorised in advance. New features and redesigns remain separate scope.
Help customers get answers and give your team less repetitive admin. We build focused enquiry assistants, workflow automation and website editing tools, with clear limits and a handover to your team.
Discuss your project
“Add AI” is not a complete brief. We start with a repeated task, a trusted source of information and an owner who can judge whether the output is useful. Automation follows an agreed process rather than making unsupported promises.
Prepares text, image and page updates from your instructions. Your team reviews changes before publication unless a specific low-risk action has been authorised in advance. New features and redesigns remain separate scope.
Answers from approved business information and gathers useful enquiry details. Uncertain answers and requests outside its remit go to a person. It must not invent prices, availability or commitments.
Organises enquiries, drafts follow-ups or prepares records for agreed systems. Sending external messages, confirming bookings, changing prices and taking payments require explicit permissions and suitable review steps.
We assess your CRM, calendar, email, store or booking system before promising compatibility. Available APIs, credentials and subscription limits determine what can connect. The quote lists usage costs, monitoring, supported changes and escalation arrangements.
Choose a recurring job your team can explain and check. The first brief should name the input, the useful output and the person responsible for the result.
AI can help answer questions from approved business information or prepare a summary from an enquiry. Start where source material is reliable and a colleague can check the answer. Agree how the assistant handles missing information and requests beyond its scope.
Moving a submitted form into a CRM, assigning an owner or flagging a missing field may only need a clear rule. We assess the existing tools first, then scope AI where interpreting language or preparing a draft adds a useful capability.
Illustrative project
A team manually reads every enquiry, checks for missing details and copies the same information into its system.
Capture structured details, flag missing information, prepare a handover and let a team member approve the next action.
Try the working enquiry demo. It uses explicit rules and fictional inputs to demonstrate review controls; it does not claim to run a live AI integration.
Try the enquiry workflow demo Explore labelled design conceptsPractical answers to help you prepare a useful brief.
The quote depends on the workflow, source material, connected systems, permissions and testing needed. Share a sample task, approximate monthly volume and the tools involved. We separate the build price from model usage, third-party subscriptions, monitoring and ongoing support so you can assess the full cost.
We check the named product, your account plan, available APIs and access before confirming compatibility. The scope identifies which information can be read or changed, what happens when a connection fails and who resolves exceptions. A missing supported connection may require a different approach.
The schedule follows a review of the workflow, source material and system access. The proposal sets milestones for a prototype, review, testing and release, including your team’s input at each stage. Begin with one workflow; additional systems or actions are assessed before extending the scope.
We agree the information the assistant can access and the actions it can take. Your team approves source material, review rules and escalation routes. Uncertain answers go to a person. External messages, bookings, prices and payments need explicit permissions and appropriate checks before an assistant can act.
Record handling time, corrections and missed handovers before the pilot. Compare the same tasks afterwards, including time spent reviewing outputs and resolving failures. Check answer quality and recurring costs alongside any time saved, then decide whether to expand, adjust or stop the workflow.
Choose one task and define what a useful result looks like before expanding the workflow. This worksheet is a planning aid, not a promised efficiency gain.
Discuss one workflowAutomation with a human handover.
Use your own baseline and approved examples. Include the time spent checking output and handling exceptions when assessing whether the pilot helps.
Assign responsibility for approved source material, output review, access and operational incidents. Changes to prompts, source content or connected systems need appropriate rechecking. Expansion should follow evidence from the pilot rather than an assumed return on investment.
Tell us what you have in mind. We’ll email you to arrange a short discovery call.
Prefer email? info@brandflame.co.uk
Thanks, we have your message.
We’ll review your enquiry and get in touch to discuss the next steps. Keep an eye on your inbox for a couple of call times.
We’ll review your enquiry and get in touch to discuss the next steps.
How we price your project