Private Phase 1 Partnership • 2026

SAFEGUARD
OVERWATCH

Strengthening the current platform and establishing a scalable, professionally managed technical foundation.

Frankenstein Creations proposes a focused Phase 1 technical partnership to refine Safeguard Overwatch, transition its production foundation beyond Base44, develop a professional native mobile application and introduce stronger design, quality assurance and development controls.

Safeguard Asset Protection Service × Frankenstein Creations

Technical FoundationFirebase backend architecture
Native DeliveryFlutter or React Native application
Development ControlPrivate GitHub repository
01BMonth 01 / Video Brief

The first step, explained in 10 seconds.

Meet Sentry, Safeguard Overwatch’s operational guide. In ten seconds, he introduces the three foundations of Month 1: interface refinement, native app deployment and a secure employee download portal.

Read video transcript

“Month one refines the platform, launches the native app, and gives every employee a secure place to download it.”

Next / The Technical Transition
02The Technical Transition

From rapid prototype to scalable product infrastructure.

Base44 helped accelerate the initial Safeguard Overwatch build and prove the operational concept. Phase 1 will begin transitioning the production platform to a technical foundation that gives the project stronger scalability, cleaner development control and greater long-term ownership.

The proposed production backend will use Google Firebase, allowing the platform to grow without remaining dependent on a closed application-building environment.

Current Platform

Base44 application

Phase 1 Transition

Architecture audit and controlled migration

Production Foundation

Google Firebase and native mobile application

03Scalable Backend

A backend designed for growth, reliability and control.

Frankenstein Creations will assess the existing data, users, workflows, files and application logic before creating a controlled migration plan. The objective is to move the production foundation to Google Firebase while protecting the working functionality already built.

Firebase Authentication

Secure user access

Cloud Firestore

Operational application data

Cloud Storage

Images, reports and documents

Cloud Functions / Run

Protected backend logic

Cloud Messaging

Operational notifications

Security Rules

Role-based data protection

Crashlytics & Monitoring

Issue tracking and visibility

Data Recovery

Controlled exports and procedures

The migration will be staged and tested. Existing Base44 functionality should not be disconnected until its Firebase replacement has been verified.
04Native App Foundation

Built for the field—not confined to a browser.

The mobile application will be rebuilt or packaged using Flutter or React Native, with the final framework selected after the technical audit. The decision will consider the existing code, required integrations, offline operation, maintainability and the fastest reliable route to a production-ready application.

Framework DecisionFlutter or React Native will be confirmed after reviewing the existing codebase and operational requirements. The chosen framework must support long-term maintainability rather than only the fastest short-term conversion.
01Reliable Android and iOS deployment
02Offline data capture and synchronisation
03Camera and document uploads
04GPS and location services
05Push notifications
06Secure authentication
07Device permissions
08Improved mobile navigation
09App versioning and controlled releases
05Development Control

Clean code. Controlled changes. A recoverable development history.

The project will be connected to a private GitHub repository so that development is no longer dependent on changes made inside one platform. This creates a controlled technical record of the Safeguard Overwatch product and gives the development team a safer way to improve, review and release the application.

GitHub provides source control, development history and code recovery, supported by separate Firebase data-export procedures.

Private source-code repository
Protected production branch
Separate development and feature branches
Pull-request reviews before important changes
Issue and bug tracking
Release history and version tagging
Automated linting and build checks
Technical documentation
Controlled contributor access
Environment variables kept outside the source code
Version history and recovery when a change causes problems
06Product Design & Quality

Lizemari Franken / Phase 1

Technical development supported by experienced product design.

Lizemari will support the project with focused UI/UX improvements, interface consistency, user-flow reviews and experience-based quality assurance. Her role is not to redesign the complete platform unnecessarily, but to identify friction, improve priority screens and create a professional design foundation that development can follow.

View Lizemari’s Portfolio
UI/UX design
Figma
Wireframes and user flows
Mobile application interfaces
Dashboard design
Responsive prototyping
Interface consistency
Developer handoff
User-experience QA
07Shared Product Vision

Michael remains directly involved in shaping the platform.

A dedicated Figma workspace will be created for Safeguard Overwatch. Michael, as the client and product partner, will receive full collaborative access to review screens, leave comments, suggest changes and help shape the platform around his operational experience and long-term vision.

The Figma workspace should become the shared visual source of truth between the client, designer and development team.

Michael’s Operational Vision
Figma Wireframes and Prototypes
Review, Comments and Approval
GitHub Development
Testing and Release
Existing-interface audit
Shared design file
Core colour and typography system
Reusable component library
Priority user flows
Improved mobile screens
Clickable prototypes
Developer specifications
Approved design history
Michael does not lose control of the vision. The process gives him a clearer way to guide it.
08Month 1 Delivery Plan

Four focused weeks to establish control and momentum.

Week 101

Audit & Architecture

  • Review the current Base44 build
  • Map data, users, files and backend logic
  • Review bugs and priority interface issues
  • Assess Flutter versus React Native
  • Create the private GitHub repository
  • Create the shared Figma workspace
Week 202

Firebase & Design Foundation

  • Configure the Firebase project
  • Establish authentication, database and storage structure
  • Begin controlled data-migration planning
  • Complete the UI/UX audit
  • Define the reusable Figma design system
  • Confirm the native framework
Week 303

Native Build & Priority Improvements

  • Establish the native application shell
  • Connect the first Firebase services
  • Implement priority navigation and interface improvements
  • Begin device and operational testing
  • Record bugs and feedback through GitHub
Week 404

Integration, QA & Handover

  • Test priority workflows
  • Resolve critical Phase 1 issues
  • Verify Firebase security and access rules
  • Prepare an internal native test build
  • Review the updated experience with Michael
  • Create the next prioritised development backlog
09Expected Outcome

A stronger product foundation with shared control.

A documented technical architecture
A private and controlled GitHub repository
A configured Firebase production foundation
A confirmed native application framework
An internal native application test build
Priority UI/UX improvements
A shared Safeguard Overwatch Figma workspace
Michael’s collaborative access to designs and decisions
A documented bug and improvement backlog
A safer path away from platform dependency
Phase 1 establishes the foundation and begins the controlled migration. Final feature parity and full removal of the previous backend dependency will happen only after the migrated functionality has been tested and accepted.
10Next Step

Approve Phase 1 and begin the technical transition.

The immediate goal is to give Safeguard Overwatch a scalable backend, professional native-app direction, controlled development workflow and collaborative product-design process—without losing the operational knowledge and functionality already built.