Tell Me What’s Stuck

Frequently Asked Questions

  • What kinds of companies do you work with?
    I work best with companies that depend on software or information-heavy processes and want an experienced technical partner who can see beyond one narrow part of the system.
  • Do we need a detailed specification?
    No. We can begin with the problem, the people it affects, and the result you want. If the scope is still unclear, discovery can be the first part of the engagement.
  • Can you work with our existing development team?
    Yes. I can take ownership of a defined area, add delivery capacity, review architecture or development practices, and work alongside your internal developers and stakeholders.
  • Do you only build new systems?
    No. Improving an existing system is often more valuable than replacing it. I can modernise, stabilise, integrate, or extend what you already have while protecting the parts that still work well.
  • What technologies do you use?
    The choice depends on the problem, your existing environment, and who will maintain the solution. I favour proven, understandable technologies over novelty and choose tools that fit the long-term needs of the project.
  • Do you work remotely?
    Yes. Most discovery, development, technical reviews, and ongoing collaboration can be handled remotely. If a project would benefit from on-site work, we can discuss that during the initial conversation.
  • Can you help us decide where to use AI?
    Yes. We start with your real workflows, bottlenecks, and business goals, then assess possible uses of AI according to value, feasibility, risk, and the quality of the information available.
  • Can AI automate an entire role?
    That is rarely the most useful starting point. It is better to examine the individual tasks and decisions within a role. Some may be automated, some assisted, and some should remain firmly human.
  • How do you handle confidential information in AI projects?
    Data handling is considered during discovery and architecture, not after implementation. The approach depends on the information involved, access requirements, provider terms, retention rules, and your organisation's policies.
  • Do you provide ongoing support?
    Yes. Ongoing arrangements can include maintenance, monitoring, improvements, technical guidance, and continued automation work. The level of support is shaped around what your team actually needs.
  • How much does a project cost?
    Cost depends on scope, uncertainty, and the type of engagement. After an initial conversation, I can recommend a focused assessment, a clearly defined project, or an ongoing arrangement—and explain the likely investment before work begins.
  • Will you sign an NDA?
    Where appropriate, yes. We can also begin with a non-confidential description of the problem, then put the right agreement in place before discussing sensitive technical or business details.