Skip to main content

About

We build the technology between systems.

Projectix was created around a straightforward idea: businesses increasingly depend on software ecosystems that were never designed to work together.

We build the technology between those systems — applications, integrations, monitoring platforms and automation that turn fragmented operations into connected infrastructure.

01Mission

Build dependable software that turns operational complexity into usable systems.

Most of the complexity we are asked to solve is not conceptual. It is the accumulated consequence of running a business across a commerce platform, a marketplace, an ERP, a warehouse system, a finance tool and a set of spreadsheets that quietly became load-bearing.

Each of those systems is reasonable on its own. The problem lives in the space between them — in the reconciliation, the manual re-entry, the reports that never quite agree, and the things nobody notices until a customer does.

That space is where Projectix works. Sometimes the answer is an integration layer. Sometimes it is a monitoring platform, an internal application, or a set of automated workflows. It is rarely another dashboard nobody opens.

02Principles

Six things we hold to.

These are the standards we are willing to be judged against, including by the people who inherit our systems.
  • 01

    Engineer for reliability

    Systems that handle business-critical work have to behave predictably, including when something upstream fails.

  • 02

    Solve real operational problems

    We start from the process that is actually causing friction, not from the technology we would like to use.

  • 03

    Design for clarity

    Interfaces should make the state of the system obvious. Ambiguity in operational software is expensive.

  • 04

    Build security into the system

    Access, credentials and data handling are architectural decisions, taken early and revisited deliberately.

  • 05

    Keep technology maintainable

    Typed, documented, conventional code, because most of a system's life is spent being changed.

  • 06

    Measure what matters

    Logging, metrics and reporting that answer operational questions rather than filling a dashboard.

03What we are building

Proprietary products alongside bespoke work.

Projectix develops its own software as well as client systems. The two feed each other: product work forces us to solve problems properly, and client work keeps us close to how operations actually run.

Our current product focus is MAP Protector, a brand protection and commerce monitoring platform for manufacturers, distributors and brands that need to monitor advertised marketplace pricing against their Minimum Advertised Price policies.

It is in development. We are building the monitoring engine, the policy rules and the marketplace integration layer, and we are talking to businesses that live with this problem so the first release solves it rather than approximating it.

Alongside that, we take on bespoke engineering: integrations, internal platforms, data systems and automation for businesses whose operations have outgrown the tools available to them.

Straight answers about where we are.

Plenty of technology websites imply more than they can support. We would rather be useful. If you need something we have not listed — a certification, a reference, a specific integration already in production — ask, and you will get a direct answer rather than a carefully worded one.

Ask us anything
  • Products

    MAP Protector is in development. We do not describe it as generally available.

  • Marketplace access

    Amazon marketplace integration is in development, subject to applicable authorisation and API policies.

  • Certifications

    We do not hold or claim ISO 27001, SOC 2 or PCI certification.

  • Client work

    Confidential unless a client has agreed to be named.

Work with us

Tell us what is not working.

The most useful first conversation is about the process that keeps breaking, not about technology.