About
Tech work doesn’t have to feel alienating to be done well.
Spyteware Studio exists because too many small orgs, activists, and community teams are forced to choose between competent tech and values-aligned tech. You shouldn’t have to make that tradeoff.
I build systems that are calm, accessible, and secure by default — and I explain them in plain English so you can actually use and maintain what you’re paying for.
Who I am
I’m Vincent, the person behind Spyteware Studio. I work at the intersection of web development, automation, IT support, and digital safety — especially for teams supporting vulnerable people.
My background spans service desk work, system administration, custom scripting, and nonprofit tech support, with an educational background in cyber security. That means I don’t just build things that work — I build things that are supportable, documented, and resilient when something goes wrong.
I’m also deeply invested in accessibility and harm reduction. That shows up in how I design interfaces, choose tools, write documentation, and scope projects realistically.
At a glance
- Web development (Eleventy, modern CSS, static-first)
- Automation & scripting (Python, APIs, Google Workspace)
- IT systems thinking (access control, documentation, handoffs)
- Digital safety & threat-aware design
Why Spyteware Studio
Spyteware Studio is intentionally small. I don’t outsource your work, and I don’t disappear after launch. The goal is long-term sustainability — not flashy tech that becomes a burden six months later.
People-first by design
Accessibility, clarity, and consent aren’t add-ons. They’re baked into how projects are scoped and built.
Security without paranoia
Sensible defaults, least privilege, and practical guidance — not fear-driven decisions or overengineering.
You own your tools
No vendor lock-in. No mystery platforms. You get the code, the docs, and the knowledge to move forward.
How I work
I aim for calm, transparent collaboration. That means fewer surprises, clearer timelines, and systems that feel understandable even if you’re not “a tech person.”
You’ll always know what I’m building, why it matters, and what comes next. If something isn’t the right fit, I’ll say so — and help you find a better option.
Clear scope
We define what success looks like before any code is written.
Plain-English updates
No jargon walls. You get explanations you can act on.
Thoughtful handoff
Docs, training, and support so you’re not stranded after launch.
Past clients
Who I’ve supported
Most of my work is with small teams doing real-world community work — people who need systems that are practical, affordable, and actually usable.
Types of clients
- Local political organizations
- Small nonprofits
- Small businesses
- Individual community members
Why they reach out
Things feel messy, risky, or overwhelming — and they want calm, competent help.
What they value
Clear scope, plain language, and tech that doesn’t create more problems.
What they get
Systems that are safer, easier to maintain, and built for real teams.
Let’s build something you can trust
If you want tech that respects your people, your time, and your capacity, we’ll probably work well together.