LAB4CODE

Independent software · South Tyrol, Italy

The work can’t stop.
Neither can the software.

Registration, scheduling, and event operations, built for the day the person who set it up is on holiday.

Lab4Code builds web apps, admin tools, and automations around the work people actually need to do.

Start a build brief Explore the work

Open these now

Selected work

The work is the proof.

Public site · Private alpha

Auto Cron

Your calendar plans itself around what is already on it.

People fitting recurring tasks around existing commitments.

Explore Auto Cron
The workflow
Recurring work needs time on the calendar without ignoring the commitments already there.
Lab4Code’s role
Scheduling product and its public website.
What’s built
A scheduling workflow that takes calendar constraints into account, with a public site introducing the product and its private alpha.
  1. Define tasks
  2. Set constraints
  3. Schedule

Live demo

Orderly

Every order tracked from the floor to the till.

Event teams handling orders and fulfillment.

Open the Orderly demo
The workflow
An event order passes through several hands: taking it, printing it, tracking it, and settling it.
Lab4Code’s role
Event ordering application and interactive demo.
What’s built
A connected workflow for entering orders, printing, tracking progress, and settlement, available to explore in a live demo.
  1. Order
  2. Print
  3. Track
  4. Settle

Google Play · Restricted internal testing

Moodinator

A mood journal with local storage and exports you control.

People who want to record moods and review personal patterns over time.

View Moodinator
The workflow
Mood check-ins need to be quick to record, useful to revisit, and honest about how sensitive data is stored and exported.
Lab4Code’s role
Android app, privacy documentation, and Play preparation.
What’s built
Mood logging, searchable history, descriptive insights, local reminders, app lock, and user-controlled plaintext exports and backups.
  1. Check in
  2. Review history
  3. Export by choice

Google Play · Restricted internal testing

Zen Mode

Screen-time limits you set yourself, enforced on your own device.

People aged 13 and older who want configurable screen-time boundaries on their own device.

View Zen Mode
The workflow
Attention boundaries need transparent controls, local processing, and a clear path for disabling Android Accessibility access.
Lab4Code’s role
Android app, accessibility disclosures, privacy documentation, and Play preparation.
What’s built
User-configured feed, website, daily-limit, timed-visit, and rolling-window rules enforced locally with Android Accessibility access.
  1. Choose rules
  2. Enable access
  3. Review or disable

Tools Lab

Small tools.
Specific jobs.

A collection of browser utilities for moving music playlists, organising reading data, and exploring photos.

Explore the Tools Lab

11 tools you can open

  • Leaveify
  • Readwise Tags Mapper
  • Photo Journey
  • Pace Calculator

The collection changes as tools get built or retired.

Capabilities

The same three problems, again and again.

Different industries, the same shapes. If your problem looks like one of these, it has been solved before.

Registration & admin

Give people a clear way in and operators the controls, logs, and exports they need.

See TeddyDocs

Scheduling & automation

Translate recurring tasks and real constraints into a repeatable workflow.

See Auto Cron

Operational tools

Connect each step of a process so teams can see what needs to happen next.

See Orderly

Working together

Start with the workflow.

A focused first version starts with a clear problem and a shared definition of done.

  1. Map the work

    Describe the users, the current process, and where manual work gets in the way.

  2. Define the first version

    Agree the essential workflow, constraints, and what a useful result looks like.

  3. Build, review, hand over

    Review working software against that workflow and agree what operating it needs.

A useful starting point

A team with a specific registration, scheduling, or operational problem, and someone who knows how the work happens today.

Your next useful system

Bring the workflow.
Let’s shape the build.

Tell us who uses it, what’s manual today, and what you want to change. Add your deadline, constraints, and budget range. Even a rough brief helps.

Start a build brief

Opens your email app with a few prompts to fill in. The first conversation is about fit and scope.