Technical services
Product Engineering
This is the build itself — the software your customers use and the systems your staff work in. We scope it in writing before anyone opens an editor, build it on an architecture chosen for the stage of growth you are heading into, and hand over the source code, the documentation, and the deployment when it ships. Nothing here is a template with your logo on it.
Custom Web & Mobile Apps
A product built for how your business actually works, rather than the closest template you can bend into shape. One codebase serves web, iOS, and Android where the product needs mobile, so a change ships once instead of three times. We choose the architecture for the load and the roadmap you describe — and we can explain every trade-off in language you can repeat to an investor.
What you get
- A working, tested application deployed to the web and, where in scope, to the App Store and Google Play
- Full ownership of the source code, in your own repository
- Technical documentation written for the next developer, not for us
- An admin panel for the data and users your product creates
- A basic CI/CD pipeline so the next change is safe to ship
- A QA pass with a documented bug-fix cycle before release
- 30-day Hyper-Care warranty on delivered scope after go-live
What we need from you
- A clear business goal and who the product is for
- The features you want, and which of them the first version cannot launch without
- Brand files (logo, colours, fonts) if they exist
- Access to any existing system, data, or account the product has to talk to
- One person on your side who can make decisions and give feedback within three business days
Where it stops
- Anything outside the signed scope is a change order, priced before the work starts
- Ongoing feature development after launch is a next phase, not part of the build
- App Store and Google Play developer account fees, third-party licences, and infrastructure costs are yours, billed to your own accounts
- Native-only features (offline mode, device hardware) are scoped as add-ons
- Marketing, content, and campaigns are separate services — they are not folded into a build quote
E-commerce & Marketplaces
There are two very different jobs here. Selling your own catalogue is a store — that is our Website & E-commerce offer, with standard payment and shipping connectors. Running a platform where other people sell, with commissions, vendor onboarding, split payments, B2B pricing tiers, or subscription logic, is a commerce engine, and it is quoted as a custom build. We will tell you which one you are asking for on the first call.
What you get
- A customer-facing storefront on web and mobile, built for checkout rather than for a portfolio
- A super admin panel for orders, inventory, pricing, and revenue
- Customer accounts with order tracking, and transactional emails for orders and shipping
- Vendor portals with their own product management, for marketplace builds
- Payment gateway, shipping provider, and tax/VAT configuration for the markets in scope
- Commission, split-payment, and vendor-onboarding logic where the platform needs it
- Staff training on the admin panel, and 30-day Hyper-Care after go-live
What we need from you
- Your product catalogue structure: categories, variants, and how pricing works
- Preferred payment providers and shipping models, including local gateways
- Tax rules for each country you sell into
- For marketplaces: your commission structure and how vendors are approved and paid
- Product images and descriptions, or a decision to buy them as add-ons
Where it stops
- Product photography and product description writing are not included
- Ad spend and campaign management are separate services
- Standard connectors are configured; anything needing custom logic between systems is custom middleware, quoted separately
- Migrating an existing store with URL redirects is scoped as an add-on, not assumed
- Platform transaction fees, gateway fees, and licences are billed to your own accounts
Digital Transformation
The paper forms, the WhatsApp approvals, and the spreadsheet three people edit at once — replaced by one internal system that runs the workflow end to end. We start by watching how the work is actually done today, not how the manual says it should be, because software built on the org chart instead of the real process is software nobody uses.
What you get
- A written map of your current workflows as they really run, with the bottlenecks named
- A custom internal system (ERP/CRM-lite) that automates the workflows in scope
- Role-based access, so people see the part of the system that is theirs
- Management dashboards with the numbers you currently reconstruct by hand
- A staged rollout, department by department or process by process, rather than one switch-flip
- User manuals and recorded training sessions for your staff
What we need from you
- Access to how you work today: current forms, spreadsheets, and the tools already in use
- Time with the people who do the work, for interviews — usually 45 minutes each
- Someone senior who can decide when two departments want different things
- Your data, in whatever state it is in, plus a decision about how much of the history moves across
Where it stops
- Data clean-up and migration of historical records are scoped separately — messy data is a project of its own
- Staff licences for any third-party tool in the design are your own cost
- We do not change your legal, accounting, or compliance policy; we build the system that follows it
- Ongoing process consulting after rollout is a separate engagement
- This route starts with an AI & Systems Audit; we do not quote an internal system we have not mapped
System Integrations
Digital bridges between the tools you already pay for, so the same data stops being typed in three times. CRMs, ERPs, payment gateways, shipping providers, and older databases that only speak their own language. Done properly, it is the least visible work we do: it runs in the background and you notice it only when it stops.
What you get
- A middleware service that keeps data synchronised between the connected systems
- Field-by-field mapping agreed in writing before we build, including what happens on a conflict
- Error handling and retry logic, so a third-party outage does not silently lose records
- Failure alerts, so you hear about a broken connection from us and not from a customer
- Technical documentation of every connection, credential, and data flow
What we need from you
- API documentation, or access credentials, for every system to be connected
- A decision on which system is the source of truth for each shared field
- A test account or sandbox on each side, where one exists
- The person who owns each tool internally, for the questions the documentation does not answer
Where it stops
- We cannot fix bugs inside third-party software — we control the connection between systems, not their product
- If a vendor rebuilds its API, keeping up with it is a change order, not routine upkeep
- Licences and API usage fees for the connected platforms are your own cost
- Integrations built with no-code automation platforms inside an agreed workflow belong to AI & Automation Ops; custom middleware — anything built rather than configured — is quoted here
- Connections need monitoring; without a Care Plan or Automation Ops plan, nobody is watching them
Where these are sold
Custom applications start with MVP Build. Your own catalogue is Website & E-commerce (Online Store). Marketplaces, internal systems, and custom middleware are Custom Solutions, and every custom quote starts with a paid scoping step — a Discovery Sprint for a product, an AI & Systems Audit for a process. The scoping fee is credited against the build.