Connect your tools

Stop copying the same information between tools

Connect the software your team already uses while keeping important changes under human control.

Discuss a paid build

01Stop copying the same information between tools
02Let a person check important changes before they happen
03Test each connection in the job it must support

Related work

Similar products I built.

04Rental sales + operations

Congratulations—you just gave yourself five more jobs.

That is what a new rental meant for me: sell the customer, find the bike, create the booking, brief the staff and remember the follow-up. I built EREBORA because I was sick of doing all that bullshit. In one production conversation, a nine-day automatic-scooter request produced the business’s XMAX recommendation and the price stored for that turn. In another, an unusual Nusa request reached the manager group. After a booking is submitted, staff control the rental in the Hub.

EREBORA case study

EREBORA motorcycle catalog showing bikes, rental prices, and availability — Customers browse the same bikes and prices staff control in the Hub.

02Development control · Windows + Android

Software work should not stop because I leave my desk.

So I built MANTIS. It keeps long development sessions working against the real files, terminals, browsers and tests on my Windows workstation while I control those same sessions from my phone. I can switch projects, read the terminal, send instructions, stop a job and restore the same session from Android. The goal, backups, tests and recovery stay attached to the work. The workstation must remain awake and connected.

MANTIS case study

The Android app opens the same live work still running on the computer.

07Windows dictation + exact-target delivery

A perfect transcript is useless in the wrong window.

I built VoiceDictation to remember which app or MANTIS terminal started the recording. It transcribes locally and sends the text back there. If it cannot prove the destination, it saves and copies the transcript instead of guessing.

VoiceDictation case study

Real VoiceDictation Recent transcripts window with dated transcript history and copy controls — Every dictated instruction stays in a dated transcript, ready to reopen or copy.

How I work

Find what slows the work. Build only what removes it.

01Trace the job
Find where time, information, or decisions get stuck.
02Build the fix
Connect the screens, data, and tools the job needs.
03Use it on the job
Use it the same way customers or staff will.

01ClientGet the first build scopedSend me the customer or staff job you are sick of doing by hand. I’ll tell you the smallest paid build worth making, what it must do and how we will prove it works.02Remote roleHire a Full-Stack Product EngineerThe customer does not care which part of the stack broke. I work remotely. I can trace the problem from the customer screen through the backend, data and staff tools, then prove the action where it failed.