01
Websites, apps & automation
Sites, customer portals, the integrations that hold them together — booking talks to calendar, POS talks to books. Built well, maintained reliably, handed back to you so you can run it without us.
We're the folks you call when the website's acting up, the booking system won't cooperate, or somebody just tried to get into your email.
Web, security, monitoring, and the second opinion on whether you should be paying for any of it. We're in this with you.
— What we hear all week —
Our site went down before brunch.✦Who should I call about this phishing email?✦Can we take appointments online?✦The card reader keeps freezing.✦Our old web guy disappeared.✦Is this link safe to click?✦Why did the inbox stop receiving?✦Can you just look under the hood?✦
Services
The four things we get called for.
02
Security
Audits, hardening, incident response. If you handle people's data you owe them protection. Every project we ship gets the same treatment, not just the ones that ask for it.
03
Monitoring & support
We watch it. If something breaks, we tend to know before you do, and the person on it already knows your setup.
04
Software decisions, made with you
Most small businesses are paying for tools they don't use, renewing contracts nobody read, and getting quoted three times what the work costs. We sit down with your stack, your invoices, and the renewal email you've been ignoring. Sometimes the answer is “you don't need that.”
How we work
A short note about the way we run a project.
Every FridayYou hear from us.
No middlemenYou talk to the people who built it.
A note from
the shop
Re: How we'll run this
the shop
Re: How we'll run this
- 1.DiscoveryDay 0
A 30-minute call, no pitch. We hear what you're trying to do, what success looks like, and whether we're the right fit. If we're not, we say so.
- 2.ProposalWeek 1
A clear scope: what we'll build, how long, what it costs. Sometimes the right call is don't build it at all — switch vendors, drop the tool, renegotiate.
- 3.BuildWeeks 2–N
Focused weekly sprints. Every Friday at 4pm you get a written note. What shipped, what we're watching, what's next.
- 4.ReviewAt each milestone
We pause for feedback at each milestone. Security work runs throughout, not stapled on at the end.
- 5.LaunchLaunch day + 30 days
Clean deployment, written docs, a walk-through call so you can run the thing without us. Thirty days of support included; a retainer if you want us to keep watching it.
— all of us at Tenshu
No surprise billsScope only changes if we both agree.
WalkthroughYou should run what we built without us.
What we believe
What we hold to, project after project.
Technology for humans, not against them.
The work has to leave the people using it better off, clearer and safer and more in control of their own thing. If a project would only work by exploiting them, we say no.
Security is the job.
If you're handling someone's data, you owe them protection. Every project we ship gets hardened from the inside out; the way doors are part of a building.
We teach. We don't mystify.
Every project ends with a walkthrough and written docs in your inbox. You should be able to run the thing we built without calling us.
The person who writes back knows your project.
When you have questions about what we built, you're not explaining your setup to a stranger.
✦ ✦ ✦
Tell us what's going on.
A free 30-minute call. No pitch, no pressure, no follow-up nag. If we're not the right fit, we'll say so.