08
Reference desks
Counters, classrooms, forecourts, cylinder runs, and the other screens under Work.
About
A studio for operational software.
SoftzenX designs and ships the desks that schools, stations, dealers, and shops actually run. The record, the reasons to trust the work, and the team sit on this page.
01 / Record
What the studio has already shaped.
The public record is the desks, the industries, and the way a project is run. Named client numbers are added only when a project can be shared.
06
Ways in
Apps, web, automation, AI assistants, APIs, and social insights.
06
Industries
Small shops, branch desks, schools, pumps, gas dealers, and online shops.
05
Steps kept
Discuss, design, build, launch, support. The same people stay for all five.
Screens before the build
You click a desk while it is still cheap to change. The full system is written around a picture you have already used.
The notebook stays the spec
Fees, challans, nozzles, and the evening count are the requirements. The software follows that day, not a generic menu.
Reference work, plainly labeled
The desks on the site show the shape of the software. A named client is mentioned only when that project is cleared to share.
02 / Why reliable
Reliable means the desk still works on a busy day.
A launch that looks finished in a meeting and fails at the counter is not a launch. These are the checks we keep.
01
The same people stay
The person who takes the first call is still there when the desk goes live. The work is not handed to a stranger after the signature.
02
A screen the duty person can teach
If a new colleague cannot learn it in an afternoon, it is not finished. Reliability is the Tuesday queue, not a slide.
03
One record, not five chats
A sale, a fee, a delivery, or a review has a place to live. The evening total is on the same desk as the work that created it.
04
Support while the habit is new
After launch we stay for the fixes and the small changes, while staff are still learning the new close of day.
05
We will say if a tool already fits
A shelf package with a new logo is not the job. If something you already pay for can do the work, we say so before a build starts.
06
A project starts in writing
Scope, price, and timing are agreed before anyone owes a build. A form, a call, or a meeting is a conversation until that writing exists.
The seats
Direction, design, development, and support.
These are the seats on a project. One person can hold more than one. Named people on the roster above are the ones set in the studio record.
01
Direction
The owner holds the scope, the price, and the date. That person is still in the room at launch.
02
Design
Interface is a desk someone can learn in an afternoon. The screen is shown before the system is written.
03
Development
The build arrives in pieces staff can try with real records, not as a reveal on the last day.
04
Support
After go-live the same studio stays for fixes, while the new close of day is still fragile.
04 / How we decide
Three rules before a build.
The person on duty is the user.
If they cannot teach the screen to a new colleague, it is not finished.
Show the work while it is still cheap to change.
You click screens before the full system is written.
We will say if a ready tool already fits.
A shelf package with a new logo is not the job.
05 / The path
From the notebook to the first real day.
01
Discuss
We learn the queue, the bell, and the close of day. You show us the notebook.
02
Design
Screens you can click before the full system is written. We change them while they are still cheap to change.
03
Build
The working product, in pieces you can try with real staff, not a reveal at the end.
04
Launch
Records moved, people shown the desk, and the first real day watched.
05
Support
Fixes and small changes after go-live, while the new habit is still fragile.