Questions about working with Veraclins.

We create and improve software solutions, both our own and those we build with people and organisations. Our work includes research, design, product management, full-stack web development and ongoing support.

People and organisations building new products or improving existing ones. You can bring an idea, a specification, designs or an application already in use. We work across industries and take time to understand the problem and the people using the product.

Our team brings experience in research, product management, design and engineering. Members' previous work includes helping entrepreneurs find suitable peers, simplifying purchases and customer support, and improving school administration and enterprise software. We bring those perspectives together at Veraclins.

They are our leadership team. They guide company direction and engineering, product and customer research, product management, and UI/UX design, working alongside our wider team.

We want to create software that improves people's lives and work. Our products let us pursue those needs directly and keep improving the experience as we learn from the people using them.

Tell us what you want to achieve, who the product is for and where you need help. Share any research, designs or technical information you have, along with timing and budget constraints. An idea or a problem is enough to start.

Yes. We can review an existing application, build from your designs or specification, or work alongside your team. We first understand the work and agree where our involvement would help.

You lead your business direction. We take responsibility for the technical work and agree how much research, design, planning and product management you want us to take on. We raise concerns, explain options and work through decisions with you.

That depends on the work and our availability. Once we understand what you need, we can discuss a realistic start date.

We agree what the product needs to do, which work comes first and who is responsible for it. We then work through estimates, milestones and how you will review the result. Research and design are included where the project needs them.

Timing depends on the scope, complexity, dependencies and people available. We work through those factors before giving an estimate and agreeing milestones.

We agree how often to share updates and review the work together. This can include demonstrations of working software, written updates and a shared view of tasks and decisions.

Access to relevant people and information, timely feedback and someone who can make or coordinate decisions. We agree the practical details before work begins.

We explain the effect on the work and discuss the options with you. We may need to adjust the scope, order of work or delivery plan. We aim to honour our commitments and address difficulties openly.

We want software to do its job well and be straightforward to use. We review the code, test important tasks and check what happens when things go wrong. We also pay attention to the small inconveniences that make everyday use harder.

We consider the scope, expertise and delivery arrangement, then agree a price with you. Tell us your budget so we can discuss what is realistic and whether a smaller first step would help.

Billing currency and payment terms are set out in the proposal and agreement.

We clarify ownership and licensing in the agreement before work begins, including any third-party components.

We agree the handover your team needs, including access, documentation and walkthroughs. We can also provide maintenance and further development at a fair price, with an agreed scope and response expectations.

We discuss the effect on the work and follow the notice, payment and handover terms in your agreement.

We agree who needs access and how project information should be handled. Our Privacy Policy explains how we use information submitted through this website.

We agree what the software needs to do and how it will be assessed. Business results also depend on adoption, pricing, operations and market conditions. We discuss those factors when defining the work.