Make everyday work easier to manage.
Your team is chasing updates, copying information between systems and working around processes that should be helping them. You have invested in software, but keeping everything moving still takes too much effort.
I help you organise the work, connect the systems and automate the steps that get in the way. That includes hands-on monday.com implementation, Jira workflows, Make.com integrations and practical uses of AI, shaped around how your business actually operates.
Too much depends on someone remembering.
Requests need chasing, information is entered twice, and handovers depend on emails or the one person who knows what happens next.
The system is configured, but people struggle to use it.
The screens are complicated, the process does not reflect the real work, or an earlier implementation never became part of everyday operations.
You want to automate more, but need a sensible starting point.
You can see opportunities for integrations or AI, but need help deciding what is useful, what is feasible and how people will stay in control.
You may be starting from spreadsheets, improving an existing setup or preparing to expand. We begin with the work people need to do and the decisions they need to make.
The tools have grown without a clear plan. Boards, spreadsheets and applications overlap. People are unsure where information belongs or which version they can trust.
From understanding the process to making it usable.
Map the work before changing the system
I work with you and the people using the system to understand how requests arrive, who acts on them, what information is needed and where work gets held up. We agree what should be simpler and prioritise the changes, including where an existing step can be removed altogether.
Build a coherent place to manage it
I design and configure the boards, forms, records, permissions and views around that process. This can cover CRM, project tracking, applications, events or support requests. We clarify ownership and standardise the information people enter, so dashboards and reports reflect work you can trust.
Connect the steps across systems
I use native automation where it fits and Make.com or API integrations where the work needs to cross applications. That might mean carrying an approved request into the next stage, keeping records aligned or preparing a communication for review. We also decide what should happen when information is missing or a step fails.
Test with the people who will use it
I involve users in the design and acceptance of the system, working through real examples and the exceptions that do not fit the usual path. Where existing data needs to move, we plan the transfer and checks. Training focuses on everyday tasks, with documentation that explains how the system works and how to maintain it.
Improve it without making it harder to own
We can deliver changes in manageable stages, learn from use and refine the setup. I make the dependencies and ongoing costs visible, and help you decide what your team can maintain and where specialist support is useful. Continued support can be agreed around your needs.
The tools I work with
My implementation experience includes monday.com CRM and Work Management, Make.com, Jira, Jira Service Management and Confluence. I have earned the monday.com CRM Pro and Work Management Core accreditations. The choice of tool follows the process, the people and the systems you already use.
What better work management can look like
BF Games | Improving how work moves between teams
BF Games wanted to improve how work was prioritised, started and handed between teams. I introduced backlog triage and a clearer intake process, improving the handover from account management to development and making the business purpose of approved work visible.
I reviewed workflows across back-end, front-end, QA and support teams, using Jira Automation to establish shared workflows with less complexity. As Scrum Master, I also mentored development and support staff. By helping the support team prioritise overdue issues, I contributed to its reduction of issues outside agreed service levels to zero.
The engagement expanded beyond development into support and marketing. For marketing, I introduced monday.com CRM and reworked the processes around it. The improvements connected priorities, handovers, collaboration and day-to-day decisions across departments.
Techie Nesters | Making the system fit the community
Techie Nesters had a partly working monday.com setup after earlier attempts had failed to meet its needs. The people using it needed something intuitive, and the design had to reflect the business’s priorities and values.
I consolidated the requirements into a phased plan and extended the CRM to support events, technical-support requests, applications and community-assistance workflows. Make.com handled steps beyond the native automations. The client was directly involved in design and acceptance.
The result was a more coherent operational platform to support day-to-day work and future expansion, with end-to-end documentation to reduce dependency. The client subsequently asked to continue working together under a retainer.
Ragan Technical Solutions | Simplifying an existing setup
Ragan needed clearer project tracking, better data quality and a less cumbersome billing process across its monday.com CRM and Work Management environment.
I reviewed the setup and agreed a programme of improvements with the client. The work simplified project tracking and billing, included support for a QuickBooks integration, and standardised data entry through Superforms. I also reviewed, improved and created automations. The engagement produced a simpler operating approach, improved data quality and more effective workflows.
Use AI where it earns its place
For a step with clear rules, I start by considering straightforward automation. Where the task involves interpreting text, finding relevant information or preparing a draft, we can explore whether AI is useful. Possible starting points include summarising incoming requests or drafting routine communications for someone to check.
We agree what a useful result looks like, test it against real examples and decide what needs human review before it affects a customer or the next stage of work. Access to information, handling exceptions and responsibility for decisions are part of the design.
Experience from my own product development
On AudioGuide, my independent museum-guide product initiative, I use AI to support architecture, implementation, research and draft translations. I work in bounded increments, review proposed changes and verify the results. The process also identifies where specialist review is needed before release.
That experience informs how I assess AI opportunities with clients: define a useful task, give it the right context and check the output. It does not remove my responsibility for the work.
A focused improvement or a wider implementation
We can start with a review of your current setup, a defined workflow that needs improving, or a broader implementation. I can design and build the changes, work alongside your team and provide the training and documentation needed to take ownership.
I will explain the choices, challenge unnecessary complexity and tell you when a simpler process would solve the problem. We agree scope, priorities and responsibilities before the work begins, and adjust them openly as we learn.
Which part of the work takes more effort than it should?
Tell me what your team is trying to do, which systems you use and where things become slow, repetitive or unreliable. You do not need a finished specification or a decision about the technology before we talk.
