Question 1

Do I have to use HelixScribe?

Accepted Answer

No. Using my development experience doesn't automatically mean moving your organisation onto HelixScribe.

I might improve the systems you already have, build something specific to solve a defined problem, or explore whether existing functionality within HelixScribe could support your organisation. The right option depends on your requirements, budget, existing infrastructure and what will be practical to maintain.

Question 2

Who owns my data and the work you develop?

Accepted Answer

Your organisation should retain control of its own data, with appropriate access, export and deletion arrangements.

For custom-developed work, ownership, access to source code, licensing and ongoing maintenance are agreed according to the work being commissioned. If you choose to use HelixScribe, access to the platform, your data, support responsibilities and the process for leaving the service are defined separately. Either way, the arrangements should be understood before a system becomes operationally important.

Question 3

What happens if you're unavailable?

Accepted Answer

It's a reasonable question, particularly when an organisation is considering relying on software developed by a small business.

I work with conventional development technologies and keep my software projects in version-controlled repositories. This makes it possible to document, review and maintain code in a structured way.

However, having readable code is only part of business continuity. A dependable operational service also needs appropriate access arrangements, backups, documentation, security measures and a plan for ongoing support. The requirements vary depending on whether I'm developing a standalone website feature, providing a limited pilot or supplying a system that your team relies on every day.

Before an important system goes live, I aim to establish the relevant support, recovery and exit arrangements, including how responsibilities would be handled if I could no longer provide the service.

I won't pretend that every prototype comes with the infrastructure or contractual commitments of an established enterprise software provider. What I can do is be transparent about what is available, what is required and what needs to be put in place before an organisation depends on it.

Question 4

Does custom code create more risk?

Accepted Answer

It can, particularly when systems are poorly documented, difficult to maintain or dependent on one person's knowledge.

But established platforms have dependencies too. A WordPress website might rely on numerous plugins, licences and third-party developers. A CRM may make data export difficult or require expensive upgrades. An automation might depend on several services continuing to work together.

I don't assume that custom code is automatically better, or that a widely used platform is automatically safer. Instead, I look at the practical trade-offs:

- How well does the solution meet your requirements?
- What will it cost to implement and maintain?
- Who can support it?
- How easily can it be changed?
- What happens if a service fails or a supplier becomes unavailable?
- Can your organisation retrieve its data and move elsewhere if needed?

These questions matter regardless of which technology we choose.

Question 5

What does ongoing support look like?

Accepted Answer

It depends on what's being delivered. A standalone website feature, a limited pilot and a system your team relies on every day need different arrangements.

Before an important system goes live, we agree what support involves and who is responsible for what. Details such as response times are set out in the service agreement for that project, rather than promised in general terms.

Question 6

How do you approach security?

Accepted Answer

Security measures are agreed according to the information a system handles and how it will be used. Code is tested and reviewed before it's used operationally, whether or not AI helped to write it.

As with continuity, I'll be clear about what is already in place and what needs to be put in place before your organisation depends on a system.

Question 7

How do you use AI in development?

Accepted Answer

AI-assisted development is part of my workflow. I use AI tools to help investigate problems, develop and review code, explore different approaches and test how systems behave. This can make development significantly more efficient, particularly when exploring prototypes or reviewing existing functionality.

But AI-generated code still needs technical judgement, testing and appropriate security controls. The responsibility for assessing whether a solution works, whether it handles information appropriately and whether it is suitable for operational use remains with the people developing and deploying it.

AI is a tool in my development process, rather than a substitute for accountability.

My approach: practical problem-solving, with technology that fits the job