Tonight again, it starts with copying sign-ups
You announced the event. Registrations are coming in.
You copy form answers into the Excel roster, match payments against the bankbook, send reminders one by one. When the event ends, you tally the survey — and start the next announcement.
Running a community or school tends to become a patchwork of off-the-shelf tools. Data is split across them, and human hands do the stitching. The more events you run, the deeper operations sink into busywork.
The thing you most want time for — facing your participants — keeps getting pushed to last.
But what if you didn't have to carry all of it?
Announcements, rosters, payment checks, reminders — every one of them matters, and none of them may go wrong. That is exactly why they consume your time and attention.
Until now, doing them carefully by hand was the only way. Now there is a partner you can hand them to — care included.
Run operations with AI.
There is a system doing exactly this in production, at Okage Juku, a learning community for business owners in Kumamoto.
Everything from promotion to membership operations is connected, and day-to-day operations happen through conversation with Claude.ai.
Creating events, checking sign-ups, drafting campaigns — the operator asks in chat, and AI executes.
Here is how the operator's day changes.
- "Create next month's meetup" — one conversation, and the event page is live
- A sign-up flows automatically into the roster, payments, and the check-in list. Zero copying
- Unpaid? Waitlist? Just ask the AI. No more evenings chasing entries one by one
- Who attends and who stays is always visible as data. Your next move runs on facts, not hunches
The hours you save go straight back to your participants.
It's fine if it ends with just the conversation
This is not "website production"
Plenty of agencies can build an announcement page.
The Okage Juku model is a custom-built operations platform for membership communities — schools, classes, associations, salons — that integrates event sign-ups, payments, membership, learning, and analytics in one place, with AI executing daily operations. Instead of bending your operations to a SaaS template, Nexa Engineering (Kumamoto, Japan) builds around how you actually run things, end to end from design through operation.
Okage Juku platform — everything in one place
For example — one sign-up ripples through every function
The stitching is done by the system, not by hand. Every event adds to the participant and member data automatically.
Who this fits
- Schools & classes — tuition, attendance, and student contact scattered across separate tools
- Study groups & seminar organizers — building a fresh sign-up form and roster for every event
- Associations & organizations — dues, member lists, and event operations still manual as you grow
- Salons & membership communities — monthly members and one-off events tangled together
You don't have to wait for "finished"
Custom membership-system development is commonly quoted at millions of yen and months of work. The Okage Juku model doesn't build behind closed doors until "done" — we build in stages from a minimal start, so the first step stays small.
- Free consultation — we listen to how your operations flow today (announcements, sign-ups, payments, roster, campaigns)
- Launch a minimal build — event registration only, to start. Real operation begins immediately
- Grow while operating — payments, membership, and the learning library are added as live use demands them
After launch, every next feature was built while real event registrations ran in production.
At Okage Juku too, payments and the video library were expected to take several more months to introduce — live operation made the priorities obvious, and both shipped ahead of schedule. Ship something that works, and the field shows you what to build next. That is Nexa's way: working software before requirement documents.
Why we can do this
The reason is how we build.
- AI-driven development — Nexa Engineering designs, implements, and tests in collaboration with AI. A small team that builds fast and wide
- What we don't build, we connect under the hood — proven services like Stripe (payments) and Cloudflare Stream (video) are not rebuilt from scratch, and not stitched together by people working screens. They are wired system-to-system through the connection points (APIs) each service exposes. With no human relay in between, nothing gets miscopied — and because the stability of proven services carries straight through, solid functionality comes together in a short time
- We run the same pattern ourselves — our own sales run on Hashira SFA, operated by AI. Okage Juku is the second example. We hand you a pattern we use every day, not a picture drawn to sell
- Defense is built into the flow — every AI operation is audit-logged, personal data is auto-masked in logs, the database is isolated with Row Level Security, and every release passes three stages of E2E verification. Built on the assumption of holding members' personal data
Compare for yourself
The same "digitize community operations" — with very different insides.
| Patchwork of tools | Generic membership SaaS | Okage Juku model (Nexa) | |
|---|---|---|---|
| Data connectivity | Split, copied by hand | Only inside that service | End to end, promotion to membership |
| Daily operations | All human | Learn the screens | Just talk to AI |
| Shape of features | Bend operations to the tool | Bend operations to the template | Built around your operations |
| How it grows | Relearn at every switch | Depends on the plan | Grown by live operational demand |
| Personal-data defense | Scattered across tools | Depends on the vendor | Audit logs, masking, RLS built in |
The real thing is running
This is not a concept drawing. It is in production: okage-juku.com
And the technical underside is fully public.
| Area | Technology |
|---|---|
| Frontend | Next.js 15 (App Router / Server Actions) / React 19 / TypeScript |
| Backend | Supabase (PostgreSQL + Auth + RLS) / Zod (boundary validation) |
| Payments & video | Stripe / Cloudflare Stream |
| AI integration | MCP server (26 tools) / Claude.ai connector / OAuth (DCR / PKCE) |
| Delivery & notifications | Resend (email) / Web Push (PWA notifications) |
| Security | Cloudflare Turnstile / rate limiting / PII-masking logger / audit log |
| Infrastructure & monitoring | Vercel / Sentry / GitHub Actions CI |
You don't have to commission development today
Start with a free consultation.
We listen to how your operations flow today (announcements, sign-ups, payment checks, roster, campaigns), and map out on the spot what can be automated and what order lets you start smallest.
Take the map home as it is. If it ends with the conversation, that's fine — no sales calls.
Online is fine · ending with just the conversation is fine
P.S. "Still at the idea stage" is welcome. Okage Juku also began as a minimal build — event registration only. Launch small, grow in real operation — we'll walk that first step with you.
FAQ
How much does it cost?
It depends on scale and how you start, so pricing is individual. Like Okage Juku, you can begin with a minimal build — event registration only — and grow in stages, so there is no all-at-once quote. In a free consultation we map out where to start and a rough estimate together.
What happens to our current Excel roster and form data?
Migration is part of the design. We bring your existing participant and member records in as the foundation, then switch to a flow where every new sign-up accumulates automatically.
Can we run it without IT expertise?
Yes. Day-to-day operations run through conversation with Claude.ai, with an admin console for when you want to check things on screen. That is exactly how Okage Juku is operated.
We're worried about entrusting members' personal data
Protection is built into the development flow: every AI operation is audit-logged, emails and phone numbers are auto-masked in logs, and the database is isolated with Row Level Security. Features touching member lists don't ship unless documented risk requirements are met.
How is this different from off-the-shelf membership SaaS?
SaaS is cheap to start but bends your operations to its template — and whatever doesn't fit falls back to manual work. The Okage Juku model is custom-built around how you actually operate. For standard functions like payments, we wire proven services in directly via API, so you get both fit and stability. If 80%+ of your operations fit a SaaS template, we may well recommend SaaS instead.
Can we hire you from outside Kumamoto?
Yes. Consultation, development, and operational support all work fully online, so we take on projects nationwide. Our base is Kumamoto, and we meet in person across Kyushu.