Skip to content

When none of our products fits, the team that built them builds for you.

Three ways in: software written to your requirement, an independent view of your architecture before you decide, and a sustainability calculation that stays working in your own system rather than in a PDF.

Custom software

We write our own software. We can write yours.

When no product fits, the first attempt is usually a freelancer. The trouble starts when the developer leaves: the software keeps running and nobody can touch it, because there are no docs, no tests and no handover. We work with all three.

What we do

  • Web applications and internal systems

    Web applications, internal systems and APIs for the part of your operation no off-the-shelf product covers.

  • Integrations

    Between your ERP, spreadsheets and databases, with both ends of every integration named.

  • Data and analytics

    Semantic layers, reporting and dashboards: a data structure that gives the same answer to the same question every time.

  • Installation and operations

    On-premise installation, Docker deployment, data migration and handover.

What you keep

  • Documented software: how it was installed, how it works and how to change it, in writing.
  • Tests that show what a change breaks, even when nobody remembers why the code is there.
  • A handover to your team or one you choose, so the software still works when its author is gone.
  • Ownership: code ownership and licensing terms are written into the scoping document.

Our reference is not a slide deck but our own products: Dima, UpcyMan and UpcyCarbon, production codebases we wrote and run.

Software consultancy

Before you decide, know what state the software is really in.

Before you buy a system, rewrite one, or invest in a company whose value is its software, you need an independent view of the architecture and the code as they stand today.

What we do

  • Architecture review

    We examine the codebase and the architecture where it lives: module boundaries, data flow, dependencies and risk points. Scope and method go in writing before the review starts.

  • Technical due diligence

    Before you buy a system, rewrite one, or invest in a company whose value is its software: scope and timeline are written down at the start, shaped by whether you are the buyer or the investor.

What you keep

  • Findings ranked by risk, recommended next steps, and a closing call.

Sustainability consulting

The consultant leaves. The calculation stays.

A customer, a bank or a regulator wants a calculation, with a date attached. The PDF a consultant leaves behind cannot be reproduced the following year. The team that runs your calculation also wrote the software it lives in, so you finish with a working calculation, not a document.

What we do

  • Carbon

    Corporate carbon footprints (Scopes 1, 2 and 3), product footprints, embedded emissions, GWP sets and choice of standard.

  • Water

    Water footprint, water risk assessment and target setting.

  • Waste and plastics

    Waste stream design, segregation at source, plastics reduction and recycled content, Zero Waste.

  • EU regulation

    CBAM, CSRD/ESRS and double materiality, digital product passport readiness.

  • Data

    Measurement design, unit conversion, missing-data strategy and facility modelling.

We are preparing for Türkiye's emissions trading system under Climate Law 7552. It is not offered as a service today.

Packages

Fixed-scope packages: scope and what you keep

  • CBAM readiness

    Scope

    One product group, embedded emissions, supplier data collection

    What you keep

    CBAM-ready declaration data and the facility modelled in UpcyCarbon

  • Corporate carbon

    Scope

    One reporting year, one legal entity

    What you keep

    A corporate footprint and a calculation you can reproduce

  • Product footprint

    Scope

    Per product family

    What you keep

    A product carbon footprint in an EPD-ready structure

  • Water and waste

    Scope

    One facility

    What you keep

    Water footprint, waste streams and circularity metrics

  • Zero Waste compliance

    Scope

    One facility

    What you keep

    The documentation and reporting structure for certification

  • Data infrastructure

    Scope

    Measurement design, unit conversion, integration

    What you keep

    A facility that produces its own numbers

What you keep

  • A calculation working in your own system, with its factors, activity records and audit trail.
  • A process that does not restart from zero next year: you can reproduce the calculation yourself.

Our reference is our own product: the team setting up your calculation also wrote the platform it runs on — UpcyCarbon, a production codebase we wrote and run.

Why this team

  • We wrote the software

    The team setting up your calculation built the platform it runs on. There is no one in between.

  • Founders do the work

    At a large firm a partner sells the work and a junior delivers it. Here the person who sells it does it.

  • A software team behind you

    Data collection, unit conversion, missing records: these are engineering problems, not advisory ones. We have both kinds of people.

  • The system stays with you

    When the engagement ends, the platform is yours. Next year you could run the calculation yourself.

How an engagement runs

Whichever service it is, the order is the same. Durations depend on the size of the work and are written down at the end of scoping.

  1. Discovery

    We listen to how you work: which records live where, and who needs which report or system.

    Duration 1–2 weeks

  2. Scoping

    We write down what will be done, what will not, which data you provide, and how we will both know the work is finished.

    Duration 1 week

  3. Development

    We work in stages and review the working result with you at the end of each one.

    Duration Depends on scope

  4. Handover

    We hand over with documentation, tests and training. The software or calculation keeps working when its author is gone.

    Duration 1–2 weeks

What we need from you

Your readiness decides the outcome as much as ours does. If one of these is missing, let's talk about it before we start.

  • Access to data

    To the systems and records the work depends on, from the start.

  • One named owner

    Someone on your side who can make decisions. Work that everyone owns is work nobody owns.

  • Decisions in days

    Answers to scoping questions within days. A decision that waits is work that waits.

  • Access to the site

    To see the measurement points and the process in person, especially for sustainability and data work.

Let's scope it together

Tell us what you need and by when. In a short call we will work out together which service fits and how large the work is.