This document is confidential.
Please enter the password to continue.

CasaManager — FileMaker Solution Migration


Executive Summary

CasaManager is a FileMaker-based SaaS system. This is a 4-week prototyping and feasibility engagement to test the thesis that an AI-assisted migration will meet the ROI assumptions that justify doing it at all.

We run CasaManager through our AI-assisted conversion process and get a working prototype in your hands as early as the material allows. The rest of the engagement evaluates it against real workflows. Each week we review what the prototype now does, what discovery surfaced, and how the ROM has shifted. By week 4, we have enough confidence to establish a rough order of magnitude estimate for the full migration.

The key constraint for this project is to preserve the current UI and workflow, not redesign. One important nuance: reproducing the existing FileMaker WebDirect layouts pixel-for-pixel is a riskier lift than rebuilding the same workflows with modern components. WebDirect's rendering quirks cost more to replicate exactly than to replace with clean component equivalents. The target is workflow fidelity — users recognize the app and their tasks work the same way — not a UI clone.


Investment Summary

Metric Value
Total Investment $40,000
Duration 4 weeks
Work Type FileMaker Solution Migration

Why Migrate

CasaManager on FileMaker works. It also costs roughly $140K/yr to keep running:

That spend scales with every new user. The platform also keeps Sunlight out of two compounding gains a modern stack provides:

Our proposal: put less than a quarter of your annual platform spend — $40K — toward the first real lift of the migration itself. At worst, a sharper read on what the full migration actually takes. At best, a functional prototype and validated ROI assumptions.

The risk is in the transition. CasaManager has accumulated business logic, workflows, and UI patterns over time. A migration that misses these or introduces unnecessary change will break user trust. That's why we start with conversion and discovery in parallel, not a blank-slate rebuild.


Our Approach

Our AI-assisted process reads CasaManager's schema, layouts, scripts, and business logic, then generates a web application scaffold. That scaffold is what discovery evaluates against — concrete artifacts instead of abstract requirements.

In parallel, we run discovery with your team to capture workflows and priorities the conversion can't see on its own.

Target stack: TypeScript, React, and Next.js. The converted scaffold generates onto this stack and the architecture recommendation uses it as the baseline. We'll validate fit against CasaManager's specifics and flag any place a different choice would serve you better.

Weekly reviews. At the end of each delivery week, we review what the prototype does, what discovery surfaced, and how the ROM has shifted. The picture sharpens week by week.

Early — Conversion & discovery kick off together

Middle — Close gaps, tighten the ROM

Week 4 — Go / no-go


Deliverables


How We Work

We deliver weekly. You'll see progress each week and provide feedback that shapes the next.

Billing: Invoiced monthly for completed weeks.


Timeline & Budget

4 weeks of work | $40,000 | ~6–8 weeks elapsed

Work Type Weeks Per Week Total
FileMaker Solution Migration 4 $10,000 $40,000

Structured as two 2-week sprints. The first sprint covers automated conversion and initial discovery. We then pause to let findings settle and give your team time to review before the second sprint focuses on gap analysis and feasibility.


Assumptions & Dependencies


Next Steps

  1. Review and align on proposed scope
  2. Schedule a kickoff meeting
  3. Identify stakeholder contacts and system access requirements
  4. Finalize SOW and engagement terms

Scope, timelines, and estimates are preliminary and subject to refinement following further discovery.

CONFIDENTIAL — Prepared by Proof+Geist for CasaManager.