About
Tech work can be careful without making people feel shut out.
Spyteware Studio exists because small orgs, activists, and community teams should not have to choose between competent tech and values-aligned tech.
I build systems that are accessible and security-minded by default, then explain them in plain English so you can use and maintain what you are paying for.
Who I am
I am 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 do not just build things that work. I build things that are supportable, documented, and resilient when something goes wrong.
I am 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 do not outsource your work, and I do not 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 are part of how projects are scoped and built.
Security without paranoia
Sensible defaults, least privilege, and practical guidance, without 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 are not “a tech person.”
You will know what I am building, why it matters, and what comes next. If something is not the right fit, I will 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. Just explanations you can use.
Thoughtful handoff
Docs, training, and support so launch is not the last useful conversation.
Past clients
Who I’ve supported
Most of my work is with small teams doing community work: people who need systems that are practical, affordable, and 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 steady, competent help.
What they value
Clear scope, plain language, and tech that does not create more problems.
What they get
Systems that are safer, easier to maintain, and built around real teams.
Let’s build something you can trust
If you want tech that respects your people, your time, and your capacity, we will probably work well together.