Who you'd be working with
Thirty years of building software. One person answering the phone.
I'm Shawna Pakbin. revDigit.link is my studio — a deliberately small one. I started writing code on FoxPro in the MS-DOS era, and today I build automation and AI systems for businesses that need a problem solved rather than a project managed.
Why I work this way
Small on purpose
When you hire a firm, your problem gets translated — through a salesperson, a project manager, and whichever developer happens to be free. Detail leaks at every step, and the person writing your code may never speak to you.
Working with me, the person who hears your problem is the person who designs it, builds it, tests it and maintains it. Nothing gets lost in translation because there is no translation. And with the AI tooling I've built for myself, that one person can now deliver what recently took a small team.
How I operate
What you can count on
One person is accountable, and it's me
There's no team to point at when something slips. If it works, that's mine. If it breaks, that's mine too — and you always know exactly who to call.
I'll tell you the inconvenient answer
If your idea is too expensive for the return, if a $40 tool already does it, or if I'm not the right person for the job — you'll hear that. A lost sale costs me less than a bad project costs us both.
Diagnosis before prescription
Ten years under the hood of cars taught me not to replace parts on a hunch. I find out what is actually causing the problem before quoting a solution for it.
Built to outlive the project
Software isn't finished at launch. I write it so it can be changed later — cleanly, by me or by whoever comes after me — because you shouldn't have to rebuild in two years.
Background, briefly
Why this matters to your project
Thirty years around software — from MS-DOS-era programs to the business applications companies depended on daily, through a decade as an automotive technician diagnosing faults instead of guessing at them, and back to building AI agent systems and automation today. What that history buys you is simple: I find the actual cause of your problem before quoting a fix, and I write software built to be depended on.
Judge the work, not the words
My open-source projects are public on GitHub — live, working systems you or your technical people can inspect before spending anything.
Explore the open source projectsFor the technically curious
What I work with
If none of this means anything to you, that's fine — it's my job to know it so you don't have to.
Automation
- RPA & scripted robots
- Web & browser automation
- Scheduled data pipelines
- System-to-system integration
AI & Agents
- Custom AI agents
- Chat assistants over your docs
- Self-hosted & frontier models
- Human approval controls
Applications
- Web apps (React)
- Desktop apps
- APIs & databases
- Client & internal portals
Foundations
- Node.js, Python, TypeScript
- PostgreSQL & data modeling
- Cloud or on-premise hosting
- Monitoring & maintenance
Let's talk about your problem
You'll be speaking to the person who would actually build it. Tell me what's going wrong and I'll tell you honestly whether I can help.
Get in touchFree, no obligation, no sales pitch.