ClearTinted
Selected projects · Internal tools · Low-code

Two internal tools with complex permissions

Beyond the two case studies, I have designed and built other internal tools and B2B SaaS products focused on complex workflows, role-based access and operational efficiency. For confidentiality I don't show screenshots: the diagrams are reconstructions with generic names, generated with Claude from the original design.

The problem

Two needs with complex permissions and little margin: eight departments that couldn't see each other's candidates, and a 110-person event with check-in and a jury.

What I did

I designed and built both tools in low-code, with isolation defined through pages and permissions, and a QR code that works with any phone camera, no app needed.

Impact

82 / 110check-ins recorded by QR on the day of the event, and around 2,000 candidates managed by 8 departments in a single system.

2023 · B2B · Airtable + Softr + Make

Internal recruitment platform for a multinational

An industrial multinational needed eight departments to run their own hiring processes in a single system, without any of them seeing the others' candidates, while HR kept the global view. Around 2,000 candidates, an average of 5 openings per department per month and about 20 people using it every day.

Recruitment system diagram
Global views for HR, eight pairs of pages (openings + candidates) isolated by department, and a single data model underneath. Image generated with Claude from the original design, for confidentiality.

Isolation through pages, not filters

Each department has its own openings and candidates pages, with permissions at page, block and field level. Nobody can «remove a filter» and see another team. The admin sees everything.

Recoverable applications

A rejected candidate doesn't disappear: they move to a recoverable pool for other openings, with views by profile (Product Owner, Quality). The hiring effort gets reused.

Job description separate from the opening

Descriptions live in a library and are written once; each new opening references them from a creation form. No copy and paste.

Data model, frontend and automations are mine. All the permission logic (profiles, pages, blocks and fields) is defined in the model, not on each screen. Project delivered and closed in 2023.
2,000candidates
8departments
20daily users
2025–2026 · In-person event · Airtable + Softr + Make

A 110-person hackathon: QR check-in and jury voting

A large company was running a hackathon with 110 guests, 10 teams and 7 judges, and needed to control attendance at the door and collect votes in a comparable way, on a tight deadline. Three roles: organisers, jury and participants.

Hackathon diagram: QR, voting and roles
QR check-in flow, the jury's voting card and the three role-based views. Image generated with Claude from the original design, for confidentiality.

A QR code that is a link, not a code to scan

Each guest gets a QR code encoding a unique URL with their ID. Any phone camera opens it; a webhook marks attendance and the organisers' dashboard updates instantly. No app, no scanner, no code. On the day: 82 of 110 checked in.

Five fixed criteria for comparable votes

Impact, functional development, originality, responsibility and ethics, and presentation; a 1–5 scale and a comment per criterion. Weighting is calculated automatically. The verdict is explained with data.

Judges kept apart

A judge never sees another judge's votes and «You've already voted» prevents duplicates; the organisers see the full team × judge grid in real time.

It's the project that best sums up how I work: a specific need, a short deadline and a solution that doesn't require anyone to install anything.
110guests
10teams
7judges
82check-ins confirmed by QR

Other internal tools and systems

What I'd do differently

Measure impact, not just volume

For the recruitment platform I know how many candidates, departments and people used it, but not how much time-to-hire dropped or how many recoverable applications ended up in another opening. Today I'd define that before delivery.

Want to talk about this case? Email me ↗