Services
What we build
Seven kinds of custom software. Most projects combine two or three: for example, an ordering portal connected to your accounting system.
Websites and web apps
A fast website or web app that works on any device and that your own staff can update, in one language or several.
For example
- a company website in several languages, including right-to-left languages such as Arabic
- a product catalogue built from your price list or product file
- a printed PDF catalogue made from the same content
- cookie consent that controls your analytics and advertising tags
What you get
- pages your staff can edit, or a site rebuilt from your product file whenever it changes
- each language at its own web address, set up so search engines show the right one
- enquiry forms with spam protection that reach the right person
- hosting and domain in your company's name
Usually connects to
- your CRM or email
- Google Analytics and Google Ads
- site search
- messengers for enquiry alerts
Customer and partner portals
A secure area where your customers, dealers or suppliers log in and help themselves. They see their own prices, orders and documents, so they don't need to phone your staff.
For example
- trade customers ordering at their own prices, with current stock
- invoices, statements and documents they download themselves
- product feeds for your dealers' own online shops
- a supplier area for quotes and delivery dates
What you get
- each customer sees only their own prices, orders and documents
- prices and totals worked out by the server, so nobody can change them in the browser
- several users per customer company, each with their own role
- works on phones and can be added to the home screen
- sign-up by invitation, or with email confirmation
Usually connects to
- your accounting or ERP system
- your CRM
- delivery services
- your customers' own online shops
CRM, internal tools and admin panels
One system for the work your team now does in spreadsheets, email and chats. It is built around your own records, steps and roles, and each person sees only what they need.
For example
- a CRM built around your own sales process
- contracts and approvals with a full history
- purchasing, stock and warehouse records in one place
- one inbox for email, messenger and phone conversations
What you get
- access by role, down to individual records where it matters
- exports to Excel whenever you need them
- your spreadsheets or old system's data brought across
Usually connects to
- your accounting or ERP system
- banks
- delivery services
- messengers
- your phone system
Integrations between systems
Your systems pass data to each other automatically, so nobody retypes it and the figures match. We also plan for the day one of them is down, so nothing is lost and nothing is entered twice.
For example
- online and marketplace orders sent straight into your accounting or ERP system
- payment and delivery updates shown in your CRM
- calls and chats saved against the right customer
- your own connection point, so partners' systems can link to yours with their own keys and limits
What you get
- each order sent with its own reference, so a resend is recognised, not duplicated
- a full re-check on a schedule that catches anything a quick sync misses
- an alert to a person when a sync stops or the two sides don't match
- a written description of what passes between the systems and what happens when one is down
Usually connects to
- accounting and ERP systems such as Xero
- payment providers such as Stripe
- banks
- delivery services
- WhatsApp, Telegram and Viber
- phone systems
- Gmail and Google Workspace
- public company and tender registers
How an order survives a failure
Demonstration with invented data.
The second copy carries the same reference, so it is ignored. One order, one invoice.
- Order 1042 sent: Invoice created
- Order 1042 sent again: Same reference, ignored
- Result: One order, one invoice
Another system stops responding
If your accounting system goes down, no order is lost and none is entered twice.
The order is held and sent again when the other system is back.
- Order 1043 sent: No response
- Order held: Nothing lost
- Sent again when it's back: Invoice created
A daily check compares both systems and tells a person when they don't match.
- Daily check: Both systems compared
- Difference found: Order 1044 missing
- Alert: A person is told
Switching the AI step off
Any member of your staff can switch it off without calling us. Work goes back to the manual route, and the system keeps running.
On
- Drafted by AI
- Checked by a person
- Sent
Off
- Written by a person
- Sent
- Everything else keeps working
Process automation
Invoices, reminders and reorder alerts sent automatically, on a schedule or when something happens. Your staff deal only with the exceptions, and a person stays in charge wherever judgement is needed.
For example
- a daily check that flags stuck or unpaid orders
- approvals in a few clicks instead of long email chains
- documents filled in from data you already have
- a morning summary sent to a team chat
What you get
- jobs that run on a schedule or when something happens
- an alert to a person when a step fails
- exceptions sent to the person who can act on them
Usually connects to
- team chats such as Telegram
- Google Workspace
- documents in Word, Excel and PDF
Reports and dashboards
Figures taken straight from your systems, so sales, finance and management see the same totals. Each figure has one written definition, and you can trace it back to the records behind it.
For example
- a sales dashboard combining CRM and accounting data
- a weekly operations report sent automatically
- stock, orders and unpaid invoices on one screen
- call-quality trends for each of your criteria
What you get
- definitions agreed with the people who use the figures
- charts and exports your team can use
- reports sent on a schedule by email or chat
Usually connects to
- your accounting or ERP system
- your CRM
- Google Analytics and Google Ads
- spreadsheets
AI features in your software
AI for one clear job, tried on real examples from your business before it goes live. A person checks the result wherever it reaches a customer, a payment or a record.
For example
- sales calls transcribed and checked against your criteria
- incoming documents turned into records
- draft replies for a person to check
- meeting notes written up from the recording
What you get
- a test on real examples from your business before launch
- an off switch your staff control
- the AI provider and where it runs named in your contract
- every AI call logged with its cost
Usually connects to
- AI models from Anthropic and OpenAI
- ElevenLabs for voice
- your phone system
- your documents and records
Software for finance teams
Ledgers, billing, reconciliation and connections to the payment providers you already use. We build software only. We are not authorised or regulated by the FCA, and any regulated activity stays with you or your provider.
For example
- bank statements imported and matched to your accounting records
- payments and invoices kept in step with your accounting system
- subscription billing for your own service
Already have software? We can take it over.
We take over systems other developers built, fix what is broken and keep developing them.
How it starts
-
You give us access to the code and the hosting accounts.
-
The paid planning step includes a review of the code and hosting. You get a written plan and estimate, as with any project.
-
If any account sits in someone else's name, moving it to yours goes into the contract, with a date.
-
We write the running instructions as we learn the system, then fix and develop it, usually under monthly support.
Work we turn down
You'll hear it in our first reply, not in a third meeting.
-
Projects nobody can define yet
If nobody can say what "finished" means, we don't start building. The paid planning step exists to settle that first.
-
Work that needs a regulatory permission
If the work needs a licence or a regulator's permission, it belongs with a licensed firm, and we say so straight away.
-
Taking over a system without access
We need the code, the hosting accounts and a paid review before we agree any date.
-
Design or branding without the build
We design the software we build. For brand work or campaigns on their own, we'll point you elsewhere.
-
Extra developers with no agreed result
We take on work with an agreed outcome, priced per stage or per month.
Not sure which of these you need?
Describe the problem in a few sentences. Our first reply says which kind of work it is, or that it isn't for us.
Written reply within one working day. No sales calls.