All case studies
AI Copilots/PropTech

Adding an AI copilot to an established SaaS product

An AI copilot built into a mature Laravel application. It drafts tenant notices, summarizes repair requests and answers questions about each customer’s own portfolio data.

of active accounts adopted within 90 days
14%
of active accounts adopted within 90 days
launched as a new revenue line
Paid add-on
launched as a new revenue line
cross-tenant data incidents
0
cross-tenant data incidents

The challenge

The client’s customers were asking for AI features, and competitors were starting to ship them. The in-house team knew the product and the rental market deeply, but had no experience putting LLM features into production.

The product was a 12-year-old multi-tenant Laravel codebase holding tenants’ personal information. Strict tenant isolation and compliance with Japan’s personal information protection law were essential.

Our approach

  1. 01

    Fit the existing product

    We worked inside their codebase and conventions, so the in-house team could own and extend the features after launch.

  2. 02

    Tenant isolation by design

    Every AI request is scoped through the existing authorization layer. The model only sees data the current user is already allowed to see.

  3. 03

    Ship in slices

    One feature at a time behind feature flags, each with usage and quality metrics, so the team could see what customers actually valued.

What we built

Communication drafting

Drafts tenant notices, rent reminders and renewal guidance in polite Japanese, following each company’s approved templates.

Repair triage

Summarizes and categorizes incoming repair requests, including photos, and suggests urgency and contractor type.

Ask your portfolio

Natural-language questions over portfolio data, answered through safe, pre-approved query templates.

AI platform layer

Shared services for prompts, usage metering, billing and evaluation that the in-house team now builds on.

How it flows

  1. User in app
  2. Auth & tenant scope
  3. Copilot service
  4. Tools & data
  5. Response
  6. Usage metering

How we measured it

Each feature has its own evaluation set, built from anonymized real cases. Tenant-isolation and personal-data masking tests run in CI on every deployment.

Results

  • 14% of active customer accounts used the copilot within the first 90 days, a strong adoption rate for a new paid add-on.
  • Launched as a paid add-on plan, creating a new revenue line.
  • The in-house team has since shipped two more AI features on the platform layer without outside help.
  • No cross-tenant data incidents.

Timeline

  1. Weeks 1–2

    Discovery

    Customer interviews, codebase review, feature shortlist

  2. Weeks 3–4

    Design

    UX in the existing design system, platform-layer architecture

  3. Weeks 5–10

    Build

    Three features behind flags, beta with 30 customers

  4. Weeks 11–12

    Launch

    Pricing, billing integration, general availability

Contact

Have an AI product in mind?

Share what you would like to build, and we will help turn the idea into a production-ready product.

No technical specification required.

What happens next

  1. 1

    Share your idea

    Describe the problem, the users and the outcome you need.

  2. 2

    Discovery call

    We review your requirements together and clarify scope and constraints.

  3. 3

    Proposal

    You receive a clear scope, technical approach and delivery plan.