Custom Software Solutions

Software that fits the way you work.

For growing businesses that have outgrown spreadsheets, off-the-shelf tools or an ageing platform. We design, build and support the web platforms, portals, mobile apps and integrations that keep your teams, customers and systems working from the same data.

What we deliver

Built for your users, connected to your data.

Most projects combine two or three of these. We scope them together, so they share the same data and one team supports all of it.

Web applications and SaaS platforms

Multi-user platforms in Python, Django and Flask, with accounts and roles, payments, dashboards and the business rules that make the product yours.

Built with: Python · Django · Flask

Customer and partner portals

Self-service for the people you work with: orders, invoices, tickets, documents and approvals, behind a secure login and drawn from your own records.

Built with: Django · Odoo · REST APIs

Mobile apps for iOS and Android

Apps for field teams, approvals on the go or customer ordering, connected to your systems through a secure API, so the app and the office see the same figures.

Built with: iOS · Android · REST APIs

Integrations and APIs

Connections to payment gateways, couriers, marketplaces and banks, so orders, payments and stock move between systems without anyone retyping them.

Built with: REST · XML-RPC · Payment gateways

Websites and eCommerce

Company sites and online shops on Odoo, WordPress or Django, built for speed, accessibility and search from the first page, with stock and prices kept in sync.

Built with: Odoo · WordPress · Django

Replacing spreadsheets and legacy tools

When a process lives in shared spreadsheets, email threads or an ageing in-house tool, we turn it into software with proper records, permissions and history, and bring your existing data across.

Built with: Python · PostgreSQL · Django

How a project runs

Working software you can review early.

Every project runs in the same four stages. From the prototype on, you review real screens and working features, so decisions rest on what you can use, not on documents alone.

  1. 01

    Discover and scope

    We map the users, workflows and systems involved, then agree a written scope and what goes into the first release.

  2. 02

    Design and prototype

    Key screens and flows as a clickable prototype, reviewed with the people who will use them before the build starts.

  3. 03

    Build in short sprints

    Each sprint ends with working features in a test environment you can try, comment on and approve.

  4. 04

    Launch, support, improve

    A planned launch with your data in place, then fixes, updates and new features as your needs change.

Prefer to run the project yourself? We can add a dedicated Python developer to your team instead. Resource Augmentation & White-Labeling

Selected work

Software we have already shipped.

Selected projects from our case files, and what one client said about our web development.

Technologies we work with

  • Python
  • Django
  • Flask
  • PostgreSQL
  • REST APIs
  • XML-RPC
  • Odoo
  • WordPress
  • iOS
  • Android
  • Payment gateways

Questions

Before you commit.

Can you build on what we already have?

Yes. We can start a new product from scratch, take over an existing codebase after a review, or add new software alongside the tools you already use.

Who owns the code?

You do. You get the source code, documentation and admin access, and the software can run on hosting you control.

How do you estimate the cost?

We scope first. After discovery you get a written scope and an estimate for each phase, so you approve one release at a time. For ongoing work, a dedicated developer is often the better fit.

Will it work with Odoo and our other systems?

Yes. Most of what we build connects to something: Odoo, a payment gateway, a courier, a marketplace or a bank. We connect through REST or XML-RPC APIs, so each record is entered once and stays in step everywhere.

What happens after launch?

We stay on for fixes, updates and new features, or hand over to your own team with documentation and a walkthrough of the code. You can switch between the two later.

Next step

Tell us what the software needs to do.

Share the problem, the people who will use it and the systems involved. An engineer replies within one business day with questions and next steps.