Skip to content

Privacy-first • Accessible • Practical automation

Useful tech for small teams that need things to work, last, and make sense.

I build maintainable websites and workflow automations for small orgs, mutual aid projects, and community teams. The work is privacy-conscious, accessible, and documented so you are not stuck guessing later.

Clear scope + timelines Documentation included Accessible UI by default Security-minded setup

A clear build process

You do not need a polished technical brief. Bring the problem, the constraints, and what you have tried. I will help shape the path from there.

  • We start with your goals, constraints, and the people who will use the thing.
  • I propose a clear scope and timeline before the work starts.
  • You get the finished work plus documentation you can return to.

Websites

Clean, responsive, accessible builds for org sites, campaigns, and resource hubs.

Automation

Forms, scheduling, reporting, dashboards, mail merges — the work that saves time and catches dropped follow-ups.

Digital safety

Threat-aware setup and guidance for teams supporting vulnerable people. Practical steps, not fear.

How it works

A good process should make the work easier to follow. This is the shape I use to keep projects from turning into a fog bank.

1) Intake + goals

A short call or form to understand your needs, audience, constraints, and urgency.

2) Scope + plan

You get a deliverables list, timeline, and a plain list of what I need from you.

3) Build + review

You see working progress before anything ships, with room to adjust the details.

4) Launch + handoff

Deployment, documentation, and support options so the handoff is not a cliff edge.

Sliding scale, because budgets are real

If you are doing community work, cost should not be the thing that keeps you from getting competent help. I use tiers so scope can match capacity.

Solidarity

lower-cost

For individuals + small volunteer-led efforts.

Sustaining

standard

For orgs with steady funding or paid staff.

Supportive

pay-it-forward

For teams who want to help subsidize others.

What gets better

The goal is not a shiny thing for its own sake. It is less confusion, safer defaults, and work your team can keep using.

Less operational drag

Repetitive tasks become workflows, automations, or handoff steps your team can repeat without starting over each time.

More trust at first glance

Websites get clearer navigation, accessible layouts, and privacy-conscious choices that feel steady to visitors.

Safer defaults

Accounts, permissions, and incident plans are shaped around real risk, small-team capacity, and next steps people will follow.

Quick answers

If you are not sure where to start, that is normal. Here are the questions that tend to come up first.

Do you really do sliding scale?

Yes. We will find a tier that fits and keep the scope realistic enough to finish well.

What do you build with?

Modern, maintainable tools. I will explain the tradeoffs without burying you in jargon.

How fast can we launch?

It depends on scope. Small sites can move quickly; bigger work gets a timeline before we begin.

Can you help with safety concerns?

Yes. I focus on practical, threat-aware setup and guidance, especially for vulnerable communities.

Ready when you are

If you have been putting this off because the tech side feels like too much, that is a reasonable place to start. We can turn it into something solid, safe, and usable.