Skip to content
The Weekly Dev

Brussels Software Studio & Technology Publication

Est. 2022  ·  Vol. I
The Weekly Dev

Front Page

Brussels, Belgium · Software Studio

Custom Software and SaaS Development in Brussels

The Weekly Dev designs and builds production-ready web applications, SaaS platforms, internal tools, and digital products for startups, agencies, and businesses across Belgium and Europe.

Senior-led product development using TypeScript, React, Next.js, Node.js, and PostgreSQL. You work directly with the developer building the product. There is no account layer between you and the code.

From the Software Desk

Six ways the studio engages. Each one is scoped around a problem a business actually has, not a technology we want to use.

01

SaaS & MVP Development

Take a product idea to a working, billable SaaS application, with the authentication, tenancy, and billing plumbing done properly the first time.

Problem
You have validated an idea and need a version real customers can pay for, not a clickable prototype.
For
Founders with domain expertise and no in-house engineering team
Output
A scoped MVP definition that separates launch-critical from post-launch work
SaaS & MVP Development

02

Web Applications

Applications, not brochure sites: software where users log in, data changes, and correctness matters more than the animation on the hero section.

Problem
A website builder or page-builder plugin has hit its ceiling and the workarounds are now the system.
For
Companies whose product or service is delivered through a logged-in interface
Output
A React and Next.js application with server and client boundaries chosen for performance, not habit
Web Applications

03

Custom Software

Business software built around how your organisation actually works, instead of reshaping the organisation around off-the-shelf software.

Problem
Off-the-shelf software covers most of the process and blocks the part that differentiates you.
For
Established businesses with a process that genuinely differs from the market default
Output
A custom application designed around your actual workflow and vocabulary
Custom Software

04

Internal Tools & Automation

Replace the shared spreadsheet, the manual copy-paste, and the process that only one person knows how to run.

Problem
A critical spreadsheet has outgrown itself and now breaks when two people open it.
For
Operations, finance, and logistics teams running on spreadsheets
Output
An internal application with validation, permissions, and an audit trail
Internal Tools & Automation

05

Technical Consulting

Architecture reviews, codebase audits, and technical direction for teams that need a straight answer before committing budget.

Problem
A rewrite is being proposed and nobody can say objectively whether it is justified.
For
Founders without a technical co-founder
Output
A written assessment with findings ranked by risk and effort, not a slide deck
Technical Consulting

06

Agency Partner

Development capacity for design, branding, and marketing agencies, delivered behind your brand, without approaching your client.

Problem
A pitch requires technical work beyond what the current team can deliver.
For
Design and branding agencies with strong output and no in-house engineering
Output
White-label or openly credited delivery: your call, agreed before work starts
Agency Partner

Selected Work

In-House ProductIndependent technology publication

A Publishing Platform Built as a Product, Not a Blog

The site you are reading is also the studio's reference implementation: a full editorial platform with authoring, scheduling, role-based access, and generated social imagery, built on the same stack used for client work.

The Challenge

Publishing on a hosted platform meant no control over layout, no way to build a distinct editorial identity, and content locked inside someone else's database. The alternative, a static site generator, would have solved presentation but not the editorial workflow: drafts, scheduled publication, multiple contributors, and per-article social imagery all needed to work without touching a repository.

Read the Full Dossier →

What Was Delivered

  • Articles are written, scheduled, and published without a deployment
  • Every article gets an on-brand social card with no manual image production
  • Content is owned outright, in a database that can be migrated or exported at any time
  • Server-rendered pages, so articles are indexable without a client-side rendering step

Stack

TypeScript · Next.js · React · tRPC · Prisma · PostgreSQL · Better Auth · MDX · Tailwind CSS

Client engagements are covered by confidentiality agreements. Relevant work can be discussed in detail on a call.

Selected Work →

From the Technical Desk

The stack, and what each part of it contributes to a product that still works in three years.

Language

TypeScript

One language from the database schema through the API to the interface. Renaming a field becomes a compile error rather than a production bug.

Interface

React · Next.js · Tailwind CSS

Server-rendered by default, so pages load fast and are indexable. JavaScript is shipped to the browser only where the page is genuinely interactive.

Data

PostgreSQL · Prisma

Relations, constraints, and transactions enforced by the database itself. Application code is not the last line of defence for data integrity.

APIs

tRPC · REST

Internal calls use end-to-end type inference; anything a third party consumes gets a documented, versioned REST interface.

Identity

Sessions · OAuth · Role-based access

Authentication, password recovery, and permissions built once as infrastructure, instead of re-checked ad hoc in each feature.

Operations

Docker · CI/CD · Cloud hosting

Every change moves through the same pipeline to a preview environment before production. Releases stop being events.

Automation

Scheduled jobs · Integrations · AI where it earns its place

Background work, system-to-system synchronisation, and, for genuinely unstructured input, a model in the loop. Not on principle.

Latest from The Weekly Dev

How We Build

Every engagement follows the same five stages. You work directly with the engineer building the product at each one.

  1. Briefing

    A conversation about the problem, not the technology. What the software has to do, who uses it, what happens today, and what a good outcome looks like in six months.

  2. Product & Technical Assessment

    Feasibility, risk, and the decisions that will be expensive to reverse. Sometimes the honest conclusion is that the project should be smaller, or that an existing product already solves it.

  3. Scope & Architecture

    A written scope with an explicit list of what is excluded, alongside the data model, integration points, and infrastructure plan. Both sides agree what done means before work starts.

  4. Incremental Delivery

    Work ships continuously to a live environment. You use the product while it is being built, and changes in direction happen while they are still cheap.

  5. Launch & Continued Support

    Deployment, monitoring, and handover documentation. Most engagements continue at a reduced cadence afterwards, but the codebase is written so that another team could take it over.

Brussels & Europe

The studio is based in Brussels and works with clients across Belgium and the wider European Union. Being in the CET/CEST timezone means overlapping working hours with almost every European client, and meetings in person are practical within Belgium.

Remote collaboration is the default. Projects run in your tools and your rhythm. The location matters for the timezone and the legal jurisdiction, not for where the work happens.

Based in
Brussels, Belgium
Timezone
CET / CEST
Serving
Belgium · Netherlands · Luxembourg · France · Germany · European Union

Start a Project

Have a product, platform, or workflow to build?

Send a short brief: the problem, the current stage, and roughly when it needs to exist. You get a straight answer on feasibility and approach, from the developer who would build it.

Software & SaaS Development in Brussels | The Weekly Dev