BUILT FOR REAL WORKVILNIUS, LITHUANIA

I build the tools
I wish we'd
already had.

Operations at a Vilnius furniture company. I build the tools we run on.

REAL TOOLS. REAL SCREENS. ACTUAL USERS.
A few things I've built01 — 03
NOT JUST CONCEPTSBuilt to solve
actual problems.
26 → 25Panels to CNC programs
in a single export
1,057Automated ShopFlow
tests
1Paid CAM licence
replaced

Follow one kitchen through the shop

Every screen below is a screenshot of my working apps with sample data loaded. The part list exported in step 4 is the same file the nesting app reads in step 5.


Work that made a difference.

ShopFlow and Nesting carry the most weight: production runs through one, every board is cut through the other. All four are public on GitHub as demo builds with no customer data.

More tools

Smaller headaches, same approach

Desktop and machine tools

Behind the screens: CAD and CAM automation


Two problems with no off-the-shelf fix

Drawings took the engineer hours and still had mistakes. The CNC's control software was hard to read and had no vendor support. Both needed tools that fit the machines and people we have.

3D model→views + dimensions→parts & hardware tables→PDF set
In useDesign · Production

Automatic manufacturing drawings

Shop drawings generated from the 3D model, no manual drafting.

ProblemEvery cabinet needed a drawing for the shop floor. The engineer drew them by hand in SolidWorks, slowly, and mistakes reached production.
BuiltTwo generators that make the same kind of sheet with no manual drafting. One is inside the cabinet creator. The other works on full kitchens modelled in SolidWorks.
What a sheet contains
  • Front, without-fronts and side views at 1:15, with front dimensions in bold and gaps marked separately
  • Parts table with material and edgebanding, plus a hardware list (runners, legs, connectors)
  • Assembly diagram with numbered balloons that match the parts table
  • Room plan and wall elevations for the whole kitchen, then one sheet per cabinet, as one PDF
  • Colours by role so shop-floor staff read a sheet at a glance. I tested and rejected transparent and wireframe styles as hard to read
13sheets generated for a real kitchen
A3 / A4one-click PDF
0manual drafting per cabinet

The first SolidWorks version ran on Python and OpenCascade. It wouldn't install on the engineer's PC, so I rebuilt it as a native SolidWorks macro rather than make him fight the setup.

JavaScript / SVGSolidWorks VBAPythonOpenCascade
In useShop floor · CNC router

A new operator interface for an old CNC

Clearer screens and a live 3D view of the cut, on the original machine.

ProblemOur CNC router runs closed control software on a touch-only Windows XP PC built into the machine. The screens were hard to read, the vendor gives no support, and the operator couldn't see the program being cut.
BuiltA complete new skin for the control software, and a companion program that shows the job live, without changing a single line of the vendor's code.
How it works
  • Read the layout of every screen out of the compiled program, so each new button lines up exactly with the touch area it replaces
  • Redrew all screens from one design system and rendered them into the exact image files the software loads: clearer type, higher contrast, tidied English messages
  • NLNCView, a small C program that runs on the old Pentium PC with no runtime. It shows the loaded program over the jog keys and follows the file the operator selects
  • Tracks the tool live by reading the coordinates the controller already shows, then draws the board being carved in 3D in real time
  • Installs with numbered one-tap scripts and an undo, because the machine has no keyboard. It never touches Windows start-up settings after one of them broke boot
0changes to the vendor's code
XPruns on the original machine PC
Livetool position and 3D cut view
C (Win32)Reverse engineeringDesign system → PNG pipelinePlaywright

Taking the same approach beyond the workshop

Two products I'm building as businesses of their own. Both started from a problem I kept seeing around me.


Everything I've built

Workshop systems, product experiments and side projects. Click a row for details.


Business first, software second

Dėdės Baldai · bespoke furniture

Operations and project delivery · Vilnius
  • Deliver customer projects end to end, from first quote to install
  • Manage B2B partners and negotiate with suppliers; sell directly
  • Designed, built and support the workshop's software: quoting, CRM, production tracking, nesting, CAD/CAM automation

Modus Group (Autobrava) · automotive distribution

Product → product development → sales development · Baltics
  • Progressed through product, product development and sales development roles
  • Worked across dealerships in the Baltic states

Vilnius University

BSc Business Information Management · 2013–2017

Operations

Project deliveryProduction planningSupplier negotiationB2B partnershipsDirect salesCosting and pricing

Product and build

JavaScriptHTML / CSSSupabasePythonOpenCascadeSolidWorks VBAExcel / XLSMWeb WorkersWebAssembly (Rust)three.jsPWA / IndexedDB

The business I build for

SWOOD DesignSCM Xilog .XXLG-codeDXF / STEPNestingBlum hardware

Languages

Lithuanian · nativeEnglish · fluent
How I work
I build next to the people who use the tool. Workshop staff and the engineer test every release.
Offline first. The shop's internet drops and a saw doesn't stop for it, so data lives in the browser and cloud sync is optional.
Decisions backed by the business's own data, like the 1,284 real programs behind the XXL rotation rule.
Plain web apps with no build step, so anyone can open them on any PC in the workshop.
I use AI coding assistants heavily. That's how one person ships this much while running a business.

Have a problem worth solving?

I'm always happy to talk about the business problem, the build, and what actually works in practice. Let's talk.

Email dalius.gervinskas@gmail.com