Where We Started,
Where We Are,
Where We're Going.

A factual look at 20 months of DeclareAll — what was in the box on Day 1, what's shipping in production today, and where the team should focus next.

• Prepared for the DeclareAll executive team.
• A shared calibration of what actually happened — so the next 12 months start from the same picture.
• Closing slide is the ask: focus on Launch and Growth.

What actually existed on Day 1

Before any code was written — this was the full inventory. Twenty design mockups. No login. No backend. No database. No API. No shipping app. Just images.

STATICAuth · Login

STATICRegister · 1/3

STATICRegister · 2/3

STATICRegister · 3/3

STATICForgot Password

STATICHome · Empty

STATICHome · All Feeds

STATICHome · Contacts

STATICStatus Detail

STATICMyWill · hero

STATICAdd Asset

STATICAdd Debt

STATICSearch

STATICNotifications

STATICConversations

STATICMessages

STATICUser Profile

STATICProfile Settings

STATICReceiver · Following

STATICReceiver · Contacts

Real Figma export delivered on the handoff — 20 static images. Not clickable, not connected to anything. Every screen above had to be built from scratch: login flow, backend, DB, API, sync, state management, i18n, notifications, biometrics, camera integration, everything.

And there was more — the handoff from the previous development team.

Before the current engineering lead joined, an earlier development team had already been engaged. What was handed over: 26 more Figma prototype frames — Lorem Ipsum placeholders, hotspot pins, "Set Ammount" typos. No running code. No backend. Still just images.

PROTOTYPESidebar Nav (10 modules)

PROTOTYPELast Will · Home

PROTOTYPEWill · Marital Status

PROTOTYPEWill · Pets (Clementine)

PROTOTYPEWill · Disposition

PROTOTYPEPersonal Belongings

PROTOTYPEDigital Assets

PROTOTYPEBank Accounts

PROTOTYPEBusiness Shares

PROTOTYPEOther Assets (Lorem)

Same category as slide 2: static Figma frames. Different origin — this is what the previous development team handed over. Same functional value: zero running software. When the current engineering role was signed on 1 Jan 2025, this was the FULL inventory inherited.

The original agreement

The Work-for-Hire agreement had a defined role, a bounded scope, and a fixed compensation.

From MVP baseline to a complete working system

In July 2025, the 14 MVP contract items were handed off as a working iOS + Android + backend baseline — not a finished product, but a stable starting point. In the same window the arrangement itself shifted verbally: scope opened up toward a full working platform, and the role, compensation and expectations were adjusted to match.

A new phase — role and expectations expanded

With the MVP closed, the company moved into a growth phase. The engineering role, compensation, and equity conversation all shifted — but with no new written agreement.

Phase 1 additions — web platform, subscriptions, KYC

None of these were in the original 14-item scope.

Apple didn't approve. So we built the moderation system.

Not once. Multiple times. Each rejection expanded scope; each fix landed without a new contract line.

Phase 2 — rework, pivots, equity crisis

Phase 3 — Marketplace, AI Voice, Vault, Legacy Library

Every rework re-cascades through 3-tier subscription config, paywalls, CRM screens, IAP products and DB seed migrations. A single "adjust the number" ask is ≈ 8–14 files touched.

The "24-hour scope" that never arrived in writing

A single, written record of the last time the team tried to lock scope in writing. No names — every step is a workflow observation, every date is verifiable from WhatsApp exports.

The same pattern, in 8 other places

Across the last 20 months, blocking items typically resolved either during a meeting or in the last day before a deadline. Below is a system-level look at where urgency propagated and where it did not.

Average wait ≈ 19 days. Median ≈ 15 days. Verbal 24–48 hour targets typically extended 5×–40× before resolution. Post-launch, this pattern is exactly what scope-lock discipline is designed to fix.

External accounts + product decisions made around engineering

Alongside the shipping track, a second track ran on email and shared docs. Engineering was often looped in at the follow-through step rather than at the decision.

Each of these landed in the shared declareall.com mailbox. Discovery of the item and downstream follow-through belonged to whoever opened the inbox first — a coordination gap the team as a whole shares responsibility for.

Every category, every list, every knob — admin-manageable instead of hardcoded

A standard MVP would have shipped every category, taxonomy, and lookup as a Dart enum or a hardcoded constant. Here the choice was different — each was exposed as a full CRUD admin surface (model, migration, endpoints, CRM screens, i18n) so new will categories, notary types, vendor professions and post tags can be added without redeploy.

What exists now.

Same product surface, 19 months later — a real running app. Real login, real data, real users, 16 languages, iOS 18.5 on device today running the current 1.2.5 build.

LIVECommunity Feed

LIVEQuick Actions

LIVEEstate Dashboard

LIVEMemorial Map

LIVEPet Management

LIVEVendor Marketplace

LIVEConversations

LIVEProfile · Plan

LIVEProfile · Settings

LIVEProfile · Support

LIVESettings Detail

LIVEModal / Sheet

LIVEWizard Step

LIVEDetail Screen

LIVEEmpty State

Every screen backed by a real API endpoint, real database rows, real Firebase auth, real 16-language i18n.
Same product surface as slide 2 — entirely different reality.

The system underneath — 10 apps, 2 databases, 3 services.

What actually runs behind those iPhone screens. Every piece designed, coded, dockerized, deployed, hosted, DNS-wired, TLS-terminated, monitored and maintained by a single developer. Servers provisioned in-house, integrations wired in-house, backups configured in-house — no external license fees leave the company, no ops contractor on payroll.

Verified against vendor pricing pages Jul 2026. Annual billing typically discounts 10-20%. Actual varies by volume (Hive Moderation is usage-based; DocuSign per-envelope over the 100/user/year allowance). AWS S3 assumes ~200 GB/month; heavier CDN or video egress can push storage cost significantly higher. Excludes hardware costs and equity dilution avoided by not outsourcing to a dev shop.

Contract → Delivered

Beyond the ship pace itself: the platform was consolidated from 5 separate repositories (mobile · api · laravel-crm · laravel-vendor · website) into a single monorepo in Q2 2026 — an infrastructure investment that automated builds, standardized deploys, and unlocked scalable engineering for launch. Done in parallel with feature work, not instead of it — so real cumulative shipping since Jan 2025 is significantly higher than this monorepo-only 630 figure.

Legal hygiene — for the whole team, before we go live

The Nevada entity is brand new. As of today no one on the executive team has a signed written agreement with the new company yet. Roles have shifted, equity has been discussed, contributions have grown. Pre-launch is the natural moment to put all of it on paper — for every role at the same time.

This is the standard paperwork any Series-A investor, acquirer, bank or law firm will ask for on day one.
Doing it together, before launch, is simpler than doing it one-by-one under due-diligence pressure.

Next phase — Launch and Growth.

Ship 1.2.5.
Announce.
Raise.
Grow.

Once the papers are signed, engineering is heads-down until launch. No further scope conversations until we're live and the growth motion is running.