Skip to content

The studio

The same standard on every project, from the first call to launch.

We are a software studio in Budapest, a small senior team. Every project gets the same attention and the same standard of work.

About Brecon

Brecon builds custom web applications, AI automation and internal systems for companies where software has to create revenue or save hours.

We have delivered 12+ projects, every one on deadline, across these industries: hospitality, energy, automotive services, fitness, IT and business software, and media. We maintain what we build after launch, which is why we do not write code we would not want to be fixing ourselves a year later.

What we hold ourselves to

  • The same team throughout

    Whoever scoped the project builds it and hands it over.

    We do not swap the team once the contract is signed, and we do not pass you down the bench when a bigger job comes in.

  • Everything in writing

    Price, deadline, scope: all of it in the quote, before we start.

    New requirement? You get its price first, then you decide.

  • Five-year code

    Tests, types, decisions written down.

    We write code as if we will maintain it in five years. Usually we will.

  • What we measure

    Software is good when it creates revenue or replaces manual hours.

    We measure that before and after launch. Everything else is a tool.

Fixed priceitemised, in the proposal
24 hoursfirst reply on working days
The code is yoursat handover, with every credential

Companies we've built for

Gloster
Palm Group
Habibi
The Garage
Design Glass
Kék Padlizsán
Jungle Burger
D+D Solar
Fawa

How we work

Seven steps, in the same order on every project.

  1. Call

    Discovery call

    30 minutes on the project: business goal, processes, deadlines. By the end you see the realistic direction.

  2. Scoping

    Quote and scope

    A written quote with a fixed price, a timeline and a technology plan.

  3. Design

    Design and architecture

    UI designs, data model, component system. This is where extensibility is decided.

  4. Build

    Development in sprints

    A clickable preview link at every stage. You watch the progress instead of reading reports about it.

  5. QA

    Testing and QA

    Automated tests, then a manual pass across browsers and devices.

  6. Live

    Going live

    Domain, SSL, monitoring, measurement. We watch the first week together.

  7. Operations

    Support and growth

    Monthly maintenance, extensions and new features as your product grows.

Industries, and one delivered system each

  • Hospitality

    Habibi: website, table booking, a QR rail, bilingual content.

  • Automotive services

    The Garage: the tuning workshop's website, in production.

  • Energy

    D+D Solar: a marketing site with a quote request form.

  • Fitness

    Fawa: a landing page, ready for the campaign launch.

  • Media and marketing

    Palm Group: a chatbot SaaS and marketing automations.

  • IT and business software

    Gloster: an internal AI content platform, in production.

What we never cross

Three rules, and each one costs us something.

  1. There is no smaller client.

    A landing page gets the same code review and the same handover as a system that ran for months. A smaller budget means less work, never a looser standard.

  2. We publish names, not industry labels.

    Every client here stands under its own name, and you can look each of them up. What we commit to, we commit to in writing, and the code stays with you after handover.

  3. A number waits for a measurement.

    We measure it first, and the client gives written consent. Then it goes up here.

Who we work well with, and who we don’t

It works when

  • There is a measurable goal

    The software brings revenue or saves working hours, and you can say which.

  • A decision-maker looks at it

    Half an hour on every clickable preview, from someone who can decide.

  • Fixed price, fixed scope

    The proposal says what you get and what it costs. That stays the price.

  • You want someone after launch

    Maintenance, extensions and measurement from the team that built it.

Look elsewhere when

  • The date outranks the stability

    It has to ship tomorrow, and production traffic will cope somehow.

  • The cheapest quote decides

    Someone will do it cheaper, and sometimes that is the right call.

  • Hourly billing, open scope

    If the money is counted in hours, we are the wrong partner for it.

  • A boxed product covers it

    We say so at the end of the call, and we write no proposal.

What we build with

  • One language across the stack

    TypeScript, Next.js and React: the same code runs in the browser and on the server.

  • The data sits in your database

    Supabase Postgres, inputs validated with Zod, and the access is yours.

  • Mobile from one codebase

    React Native: one codebase for iOS and Android, both updated together.

  • A shop on a checkout that works

    Shopify, with the payment flow left alone. We build the store around it.

  • An interface that stays quick

    Tailwind CSS, GSAP and TanStack Query: the page loads what it needs.

  • Deploys and email in your hands

    It runs on Vercel and sends through Resend. You get the keys to both.

What people ask about us

That is why everything reaches you as we go rather than at the end. The source code, every credential and the documentation are yours on the final invoice, and the codebase is written so another developer can pick up the thread. Payment is tied to milestones, so you always pay for work that exists and that you have seen on the preview link.

Then we did our job. The code and every credential are yours, the system is documented, and your own in-house developer or another team takes over something finished. There is no lock on it whose key stays with us.

Start with a 30-minute call.

Thirty minutes, and you have the realistic direction. Including the case where we are not the right choice.