Back to about
root.co
/ Natasha Francisco
// selected work · 2026
// portfolio · v1 · may 2026
01 / 22
// hello, I'm —

Natasha
Francisco.

Co-founder & operations lead at root.co. I help property managers, brokerages and SMB owners untangle the back office, then I build the systems that keep it that way.
// based
Manila · PH
// years in PM ops
5+
// taking on clients
Jun '26
// Selected · 5 of many
northridge field & forge vesper acp propflow // root.co
5+ years inside property mgmt
root.co
/ Natasha Francisco
// hello · who you're hiring
// the short version
02 / 22
01hello

Five years inside
property management.

Before root.co, I spent five years as a virtual assistant and operations specialist inside property management firms. Residential portfolios. Commercial portfolios. AppFolio, Buildium, Rentec Direct, Propertyware. Tenant comms, lease renewals, work orders, owner statements, vendor follow-ups, month-end close. The stuff that has to happen on Tuesday whether you feel like it or not.

At some point I stopped just doing the work and started fixing it. Spotting where the same task got done four times by four people. Building SOPs that actually got followed. Writing the automation that quietly retires a recurring email thread. A few of those workflows are still running at companies I left two years ago.

"I’m not the one who’ll redesign your homepage. I’m the one who’ll figure out why your AppFolio is a mess and quietly clean it up before next month’s close." // natasha · on the job
// photo · drop yours in
Manila · 11.42 PM
Natasha Francisco · co-founder · root.co
root.co
/ Natasha Francisco
// services · what I can build for you
// pick one or stack them
03 / 22
02what I do

Four ways
I’m useful.

Most clients hire me for one of these four. A handful keep me on for all four, which is when things really start to settle. Pick what matches your mess.

// 01 — ops

PM virtual assistance

Day-to-day back office for property managers and brokerages. Tenant comms, lease tracking, work orders, owner statements, vendor coordination, month-end close. I work US hours when you need me to.

AppFolio·Buildium·Rentec·Propertyware
// 02 — setup

PM platform setup & cleanup

Migration, configuration, data cleanup. If your AppFolio is half-onboarded, your owner contacts haven’t been audited since 2022, or you’re moving from spreadsheets to a real platform — that’s the project.

data migration·chart of accounts·tenant ledgers
// 03 — automate

Workflow audits & automation

I sit with your team for a week, find the four things eating their Tuesdays, and build the SOPs and automations that retire them. Owner reporting, renewal pipelines, vendor follow-ups, late-rent flows.

Zapier·Make·SOPs·email templates
// 04 — bridge

Ops ↔ tech bridge

When you’re hiring root.co’s engineers to build you a dashboard or platform, I’m the one who keeps it grounded in how your business actually runs. I scope, I translate, I run the rollout.

discovery·spec writing·UAT·training
root.co
/ Natasha Francisco
// the work · five pieces
// pick any to skip to
04 / 22
03selected work

Five portfolio
scenarios. Five fictional clients.

Each one is a brief I wrote, a system I built out, and the kind of outcomes that flow from doing the unglamorous work properly. The fictional clients are stand-ins for the kinds of operations I’ve actually run inside real PM firms for the last five years.

// 01
Northridge & Co.
A 27-year-old NYC brokerage. I rebuilt their owner portal workflow, automated monthly statements, and cleaned up two years of AppFolio drift.
Brokerage · ops
Apr '26
↳ 05
// 02
Field & Forge
Portland coffee roastery. I built the subscription & fulfillment ops — batch tracking, wholesale net-30, weekly roast schedule.
Retail ops
Mar '26
↳ 08
// 03
Vesper Dental
Six-clinic dental group, Austin. Shared front-desk SOP, billing reconciliation across clinics, supply & vendor coordination.
Multi-loc ops
May '26
↳ 11
// 04
ACP — Lending Ops
Private lender, $34M book. I designed the weekly partner update flow that retired their Monday spreadsheet ritual, and automated quarterly LP packets.
Lending · back office
Feb '26
↳ 14
// 05
PropFlow — PM Platform
The one I’m proudest of. Co-designed the platform with our engineers, onboarded BPG’s 184 units across 3 states, retired 8 legacy tools.
PropTech · rollout
Jan '26
↳ 17
root.co
/ Natasha Francisco
// case 01 of 05 · context
// northridge & co.
05 / 22
Case 01 · Brokerage ops // CONCEPT · 4-WK SCOPE

An NYC brokerage
whose AppFolio
was held together with scotch tape.

Brief I wrote. A 27-year-old residential brokerage on the Upper West Side. Sweet team, real reputation. AppFolio hasn’t been audited in two years, owners are emailing brokers every month asking for last month’s statement, vendor follow-ups live on someone’s iPhone. I built this scenario to show how I’d unwind that kind of operational drift.

Most of the work isn’t where the dashboard is. It’s in the duplicate owner contacts, the trust account that hasn’t been reconciled in six months, and the SOPs no-one ever wrote down. // natasha · approach note
// type
Cleanup + setup
// platform
AppFolio
// est. scope
4 weeks
// scenario size
91 owners
// 312 W 82nd · brownstone listing
— Vol. XXVII · No. 9
A quieter
kind of real estate.
Est. 1998 · Manhattan · Brooklyn · Queens
root.co
/ Natasha Francisco
// case 01 · design
// northridge & co. · system
06 / 22
case 01how I’d set it up

Owners stop emailing
for their statements.

Rebuild the chart of accounts in AppFolio. Put each owner into the portal so they pull their own monthly statement. Write the vendor onboarding SOP that nobody had ever written down. Send the brokers one digest email on Monday morning instead of three follow-up texts a day. The marketing site at the link below is the front door for the scenario; the work behind it is where the hours go.

northridge-co.com · owner portal
open ↑
root.co
/ Natasha Francisco
// case 01 · results
// northridge & co. · outcomes
07 / 22
case 01outcomes

What the design targets.

// owner self-serve
86/ 91
owners pulling their own statements monthly
// statement emails
−78%
inbound to brokers, month-over-month
// books cleanup
47
ghost units retired, contacts de-duped
// vendor SLA
3.1d
avg work-order close, benchmark 10–14d

Scope of work

  • AppFolio audit and cleanup: ghost units retired, owner contacts de-duped, trust account reconciled to the cent
  • Owner portal workflow: each owner pulls their own monthly statement, signs renewal docs, downloads tax forms
  • Vendor onboarding SOP: W9 and COI tracking, dispatch routing, follow-up cadence, all written down once
  • Weekly broker digest: renewals up, late rent, open work orders, in one email every Monday morning
  • A one-pager describing how the business runs — useful for onboarding new brokers
The brief I wrote for this one is the same brief I’ve walked into three real brokerages with. The numbers above are what well-run small brokerages look like, not made-up. // natasha · on the spec
Open the demo site
root.co
/ Natasha Francisco
// case 02 of 05 · context
// field & forge coffee co.
08 / 22
Case 02 · Retail ops // CONCEPT · 4-WK SCOPE

A coffee roastery
running fulfillment
out of a Google Sheet.

Brief I wrote. Small-batch roastery, roasts Mondays, ships by Friday. Subscriptions live in one spreadsheet, wholesale invoices in another, batch yields in a notebook. The co-founder is at the cafe until midnight twice a week reconciling them. Built this to show how the same operations thinking applies outside property management.

Coffee businesses fail at fulfillment the same way PM firms fail at owner statements. Different vocabulary. Same drift. // natasha · approach note
// type
Fulfillment setup
// stack
Shopify + Recharge
// est. scope
4 weeks
// scenario size
34 SKUs
// lot 24 · yirgacheffe · honey
Roasted Mon.
On your door
by Fri.
FIELD & FORGE YIRGACHEFFE
root.co
/ Natasha Francisco
// case 02 · design
// field & forge · system
09 / 22
case 02how I’d set it up

One source of truth, Monday to Friday.

Subscriptions in Recharge. Wholesale in Shopify. Batch yields in a small back-office tool. All three talk to each other and roll up to one Sunday-night screen that tells the owner exactly what to roast Monday. A Sunday-night dashboard is a boring fix, and it’s the kind of fix that gives someone their week back.

fieldandforge.coffee
open ↗
root.co
/ Natasha Francisco
// case 02 · results
// field & forge · outcomes
10 / 22
case 02outcomes

What the design targets.

// subscribers
3×
subscriber count, target 60-day uplift
// MRR
$80k
subscription run-rate that the scenario supports
// owner hours saved
11h/wk
no more Sunday-night spreadsheet match-up
// shipping errors
< 1%
wrong-bag returns, benchmark for well-run DTC

Scope of work

  • Subscriber migration from a Google Form to Recharge, with no lost SKUs and no lost cards
  • Subscription SOP: pause, skip, swap-the-roast, gift, cancel — every flow written down and tested with real customers
  • Wholesale net-30 process: account opening, COI check, auto-invoice, dunning sequence
  • Sunday-night dashboard: tells the owner exactly which beans to pull and how much to roast Monday
  • Customer service playbook: refund, replace, escalate — the cafe team handles most tickets without escalating
I picked a coffee roastery on purpose — to show that the work I do isn’t about industry knowledge, it’s about how a small business actually loses Tuesdays. // natasha · on the spec
Open the demo site
root.co
/ Natasha Francisco
// case 03 of 05 · context
// vesper dental
11 / 22
Case 03 · Multi-loc ops // CONCEPT · 4-WK SCOPE

Six dental clinics
operating like six
strangers.

Brief I wrote. A dental group opens a sixth Austin location and realises the six clinics have drifted into six different businesses. Different supply vendors. Different cancellation policies. Different ways of handling insurance. I built this to show how I’d write the shared playbook and get the front desks operating from the same script — without flattening the autonomy that makes each clinic work.

The hardest part of multi-location work isn’t writing the SOP. It’s convincing six clinic managers their version isn’t the one that wins. // natasha · approach note
// type
SOP + setup
// platform
Curve Dental
// est. scope
4 weeks
// scenario size
6 clinics + HQ
// dentistry · austin · tx
Vesper.
• A modern dental group
Dentistry
that feels
unhurried.
Six neighborhood practices.
Same-day visits. Honest pricing.
root.co
/ Natasha Francisco
// case 03 · design
// vesper · system
12 / 22
case 03how I’d set it up

One front desk, six doors.

Write the shared SOPs (intake, cancellation, insurance, escalation). Set up centralised billing reconciliation across all six clinics in Curve Dental, rolling up to HQ every Friday. Consolidate supply ordering through two preferred vendors. Train the six front-desk leads over four mornings. The goal is one experience for the patient, six teams that still own their work.

vesperdental.com
open ↗
root.co
/ Natasha Francisco
// case 03 · results
// vesper · outcomes
13 / 22
case 03outcomes

What the design targets.

// no-show rate
−30%
expected drop after a written cancellation SOP
// supply spend
−15%
typical when consolidating to 2 vendors
// HQ reconcile
1d
weekly close, target down from 3–5d
// scope
6clinics
one playbook, one billing close, one HQ view

Scope of work

  • Front-desk SOP binder: intake, scheduling, cancellation, escalation, end-of-day close. One script, every clinic.
  • Curve Dental setup and weekly billing reconciliation across all six clinics, rolling up to HQ on Fridays
  • Insurance verification and appeal playbook — the kind of audit that always finds mis-filed claims
  • Supply consolidation: from many vendors to two preferred, with reorder thresholds per clinic
  • Four-morning training rollout, recorded once, given to new front-desk hires from day one
I chose dentistry on purpose. Multi-location service businesses break the same way multi-property portfolios do — the symptoms just look different from the outside. // natasha · on the spec
Open the demo site
root.co
/ Natasha Francisco
// case 04 of 05 · context
// achieve capital partners
14 / 22
Case 04 · Lending ops // CONCEPT · 6-WK SCOPE

A $34M loan book.
Run on one shared spreadsheet.

Brief I wrote. Three partners at a private lending firm. One shared Excel file. Four hours every Monday reconciling Mortgage Automator, the bank feed, and three brokers’ inboxes. Built this scenario to show how I’d work alongside our engineers on an internal tool: spec it from the way the partners actually want to look at the book, then build the operating cadence around it.

A dashboard fixes nothing on its own. What fixes Monday is what happens on Sunday night, and what the partners agree to do with what they see. // natasha · approach note
// type
Workflow + spec
// platform
Mortgage Automator
// est. scope
6 weeks
// scenario size
$34M · 47 loans
// wk 21 · 2026 · ops
The Monday
spreadsheet
ritual.
Portfolio health
78/100
↑ healthy · 1 at-risk
Capital deployed
$6.18M
↑ 2.4% WoW
root.co
/ Natasha Francisco
// case 04 · design
// acp · the system
15 / 22
case 04how I’d set it up

A Monday cadence.
A quarterly packet. Both automated.

Sit in on three Monday meetings before writing a single requirement. Map how the partners actually want to look at the book, write that into the dashboard spec. Then build the routine around it: broker submission template, weekly partner review checklist, auto-generated LP packet, covenant alert sweep on Thursdays.

app.achievecapital.com · /dashboard
open ↗
root.co
/ Natasha Francisco
// case 04 · results
// acp · outcomes
16 / 22
case 04outcomes

Monday becomes 40 minutes.
Not four hours.

// partner hours
3.4h/wk
reclaimed per partner once the cadence is in place
// covenant catches
Thu
flagged before month-end pain, not after
// LP packets
2d → 4h
quarterly packet auto-generated from the dashboard
// broker intake
1form
three brokers, one submission flow, no rework

Scope of work

  • Write the dashboard spec from sitting through three Monday meetings, not from a feature list
  • Weekly partner review SOP — 40-minute meeting, agenda on the dashboard, decisions logged in the loan file
  • Broker intake template — same submission format from all brokers, no more chasing missing fields
  • Quarterly LP packet automation — pulls from the dashboard, dropped into the firm’s deck template, partner signs once
  • Covenant alert routine — emails the partner if a loan trips a covenant on Thursday, not after the books close
I included a finance scenario to show how I’d work alongside engineers on internal tools — the ops cadence has to come before the dashboard, or the dashboard becomes another file no-one opens. // natasha · on the spec
root.co
/ Natasha Francisco
// case 05 of 05 · context
// propflow · pm platform
17 / 22
Case 05 · PropTech · rollout // CONCEPT · 12-WK SCOPE

A PM firm paying
for eight tools that hated
each other.

Brief I wrote. A property manager with 184 multifamily units across three states, patching together Buildium, Yardi, a CRM, maintenance in Trello, leasing in DocuSign, and a stack of Sheets to make it reconcile. The scenario is the biggest in the portfolio because it’s the closest to where I want to spend my time: helping a PM firm replace eight legacy tools with one operating system, and being the person who makes sure the engineering doesn’t outrun the operations.

A PM rollout doesn’t fail at the software. It fails at the data migration that nobody owns and the leasing team that nobody trains. // natasha · approach note
// type
Co-design + rollout
// units
184
// est. scope
12 weeks
// tools retired
8 → 1
// BPG · enterprise · 184 units
One system.
Eight tools
gone.
NOI
$4.62M
↑ 12%
Occupancy
94.6%
↑ 1.8
TTF
17.4d
↓ 22%
Open WO
38
↓ 14%
root.co
/ Natasha Francisco
// case 05 · design
// propflow · the system
18 / 22
case 05how I’d set it up

Write the operating spec.
Then write the migration plan.

From week one I’d sit with the leasing team, map the work-order taxonomy, and write the data-migration plan before anyone wrote a line of code. Then run the 90-day rollout: daily slack presence, week one on every standup, every clinic-meets-IT moment chaperoned. The platform is what the engineers ship. The rollout is the job.

propflow.app · /portfolio
open ↗
root.co
/ Natasha Francisco
// case 05 · results
// propflow · outcomes
19 / 22
case 05outcomes

From three platforms to one.
Without losing a tenant.

// units in scope
184
across 3 states, zero ledger breaks at cutover
// tools retired
8 → 1
approx $2k/mo saved on legacy SaaS
// time-to-fill
17d
target for a tidied-up leasing workflow
// rollout window
90d
go-live to handover, with daily ops presence

Scope of work

  • Operating spec written from inside the leasing office, not from a Notion brainstorm
  • Data migration plan and execution: tenants, leases, owners, vendors, three years of ledger history, no breaks at cutover
  • Work-order taxonomy and dispatch SOP that the maintenance team adopts on day one
  • Training rollout: four sessions per role over two weeks, recorded, reusable for the next PM firm
  • 90-day go-live support — daily slack presence, week one I’m on every standup
  • Product pitch deck in the same brand system (link below) for selling PropFlow to the next PM
This is the scenario the rest of the portfolio leads to. It’s where my five years inside PM firms and the engineering side of root.co meet on the same project. // natasha · on the spec
root.co
/ Natasha Francisco
// process · how I work
// 28 days · five steps
20 / 22
04process

A week inside
your business first.

I don’t scope from a brief. I scope from sitting next to your team for a week, watching where the work actually breaks. Then we agree on the fix in writing, with a fixed fee and a calendar. After that I do the work.

// week 0

i

Intro call & access

One 60-minute call. I ask blunt questions about how Tuesdays go. If we’re a fit, you give me read-only access to AppFolio / Buildium / your tools so I can do real homework before week one.

// you get
homework note + quote
// week 1

ii

The week of watching

I sit with your team (in person or on shadow calls) for a full week. Watch the inbox. Watch the front desk. Watch month-end close. Almost nobody does this and it’s the reason most consultants get it wrong.

// you get
findings memo
// weeks 2–3

iii

Clean up the books

Before I build anything new, I clean up what’s broken. Duplicate contacts. Ghost units. Stale vendor records. Unreconciled trust ledgers. Boring work, week-shaped, billed flat.

// you get
audited platform
// week 4

iv

Build the SOPs & automations

Write the workflows down. Build the automations. Train the people who will use them. Test on real Tuesdays, not in a sandbox. If something doesn’t land, we fix it this week, not next quarter.

// you get
SOP binder + live flows
// day 0 →

v

Handover (or keep me on)

You own every doc, every workflow, every account I touched. Some clients say thank you and run with it. Some keep me on as a fractional ops person, 10–20 hours a week. Either is fine.

// you get
everything, day 0
root.co
/ Natasha Francisco
// pricing · three packages
// fixed · written · no surprises
21 / 22
05how I charge

Three ways
to work with me.
Pick one.

One is hourly for ongoing back-office work. One is a fixed project fee for cleanup and setup. One is a monthly retainer if you want me embedded with your team. Every quote is in writing before you sign.

// pkg 01 — VA

Virtual assistance

$32/hr · US hours
Ongoing · 10–30 hrs/week typical
  • tenant + owner email handling
  • lease tracking + renewal pipeline
  • work order intake + vendor follow-up
  • monthly owner statement prep
  • weekly digest reports to leadership
  • covered platforms: AppFolio, Buildium, Rentec, Propertyware
  • monthly billing · cancel any time
// pkg 03 — retainer

Fractional ops

$2,400/mo
3-month min · 20 hrs/wk
  • I’m embedded with your team
  • weekly leadership sync
  • ongoing process work + automations
  • I sit in on platform / dev rollouts
  • I’m the one on slack at 9am US
  • scale up / down monthly after month 3
  • good fit when you’re growing past 100 units
root.co
/ Natasha Francisco
// contact · let's start
// taking new work · june '26
22 / 22 · end
06let’s talk

If your
back office is
the bottleneck

Send me a paragraph. What’s broken, how many units / clinics / clients you run, what platform you’re on. I’ll write back within a working day with whether I can help and what it would look like.

root.co
// co-founder · ops lead
Natasha
Francisco.
// nina@getroot-co.com
// based
Manila
PH · US hours
// availability
Jun '26
two slots left
// tweaks
Background
Display font
// applies to display + section titles