Care Kiro Evolves - From Nurse App to Platform

I had an important realization while developing Care Kiro. I was building an app for visiting nurses (訪問看護師), and it hit me that station manager (ステーション管理者) features are essential too. So now, in early February, I'm turning Care Kiro from a personal app for nurses into a platform that connects nurses and station managers. It has 10 users right now, and I built the nurse PWA and the landing page at the end of January.

01Why manager features matter

Even if a nurse says "I want to use this app!", if the station (the agency office) doesn't support it, they can't get full use out of it. For example:

Table 1

A personal app has its limits.

02From app to platform

It started as a personal work management app for nurses. It was simple at first, but with the shift to a platform it's now five connected systems.

Table 2

03CI/CD automation

As a solo developer, I can't survive without automation. With the system this big, deploying by hand is impossible. So I built a CI/CD pipeline with GitHub Actions. One push deploys everything.

%% GitHub Actions jobs that run after git push · as of February 5
flowchart TD
  A["git push"] --> B["detect-changes · detect changed files"]
  B --> C["deploy-landing · landing page"]
  B --> D["deploy-web · web app"]
  B --> E["deploy-station · station manager page"]
  B --> F["deploy-console · operator console"]

04What I'm building now

I'm focused on the station manager page. The main features:

• Managing the station's nurses
• Reviewing and approving work logs
• Processing expense claims
• Managing the overall schedule
• Reports and statistics

05What I learned

B2B SaaS has to consider every stakeholder. You can't just look at individual users. You have to picture first how it'll be used inside the organization.

This realization made the direction a bit clearer. Whether it can become a service both nurses and stations use, I'll only know by trying.