Platforms and apps

The system your operation needs, when the one you bought does not do what is needed. Web or mobile, from zero or on top of what you already run, built for the people doing the work and not for the demo.

Tell us about your project
The problem

Sooner or later the software you bought stops doing what your operation needs, and whoever sold it is not going to change it for you. So the team invents a parallel path just to get work done.

How you notice it
  • You pay licences for modules nobody opens.
  • Your people keep a spreadsheet running alongside the official system.
  • Customising what you bought costs more than building what you need.
  • A vendor stopped moving and the project has looked the same for months.
The delivery

What we build

Web or mobile, from zero or on top of the systems you already run. We design for the people doing the work every day, not for the meeting where the budget gets approved. We move in sprints with something usable early, because adjusting against a real screen is cheap and adjusting against a document is worthless.

What you get
  • The platform in production, with its documentation.
  • Repositories and infrastructure transferred to you.
  • No part of the system depends on us still being around.
What we have written about this

Where we have done this

Services · Platforms and apps
E-commerce · Store

From the catalogue to the payment

An online store built from zero: catalogue, cart, payments through a gateway, coupons with their usage history, and addresses carrying the tax data a Mexican invoice needs. Products are loaded in bulk from a spreadsheet, and the confirmation, verification and password emails go out on their own.

Scope
Whole store
Payments
Gateway integrated
Status
In operation
Community and tournaments · Real time

Communities, brackets and live chat

Player profiles, communities with their own announcements, tournaments with single and double elimination brackets, winners and losers advancing on their own, and the grand final reset when it applies. Chat runs over websocket and is stored, so yesterday’s argument is still there today. Sign in with an account or with Google, with every session listed so it can be closed from another device.

Scope
Communities, tournaments, chat
Real time
Chat and brackets
Status
Online
Consumer apps · Own backend

Off somebody else’s cloud

Mobile apps with their own API instead of a rented backend: sign-up, session, user data and sync on servers we run. One of them left a managed service behind and moved onto ours. On the desktop, the same idea native for Linux, Windows and macOS.

Scope
Mobile, desktop and API
Migration
From managed service to our own
Status
In operation
How we work
  1. 01 First contact
  2. 02 Diagnosis
  3. 03 Proposal
  4. 04 Sprint build
  5. 05 Ongoing support
See the full process
Ways to work together
  • Diagnosis sprint 2 weeks
  • Custom build From 6 weeks
  • Monthly team Ongoing
See the models

45 minutes to find out whether this applies to you

Four questions first, so the call starts where it matters instead of at the beginning. If in those 45 minutes we see this is not for you, we say so right there.

Answer four questions