Willow River Automation

MoveAnchor

Product tour

Features and interactive demos

Walk the tour in order: reading comfort, pipeline samples, then documents, inventory, notes, reporting, and warehouse. What loads here is static marketing built to match real screens, not a logged in tenant, so you get layout and density without running full product actions.

Everyone on the team

Light, dark, and text size

Staff set theme and text size under My Settings; the same controls carry across job details and the rest of the app. The frame below is a static job preview with sample data; the teal strip mirrors those settings and matches the in-app shell, not a separate marketing skin.

Open the comfort demo in a new tab (opens in a new tab)

Sales

Pipeline screen

The pipeline lines up stages, jobs, and customers before anyone opens a file. Static preview with sample data; same layout tokens as the product, with the teal strip for display options like My Settings.

Open the pipeline demo in a new tab (opens in a new tab)

Flagship capabilities

What we actually built, in plain terms

Below is the document builder. Try it here or book a call for a full walkthrough.

Paperwork that builds itself

Build the same signable, formula aware paperwork your office and crews already expect, without a separate PDF tool. Drag and drop layout with headings, inputs, dropdowns, calculated fields, and signatures in one place. Variables line up with billing style tokens. A read only preview flips to a customer style view before you publish.

Before: Word, print, scan. After: one template, one link, signed in the browser.

  • Layout: structure, inputs, blocks for move day.
  • Formulas & variables: estimate to invoice in sync.
  • Signatures: in browser, in the flow.
Preview
Heading

Truck check in

Paragraph

Crew completes this before wheels roll.

Text
Number
Signature
Signature

Demo note. Screens here will move as we ship. Treat them as a taste of how the fully functional product looks during alpha, not a promise that every pixel will match your own tenant on day one.

Inventories that just make sense

Inventory is its own object: link to a customer and reuse across jobs, or attach several on one job when pickups, drops, or lists need to stay separate. Itemized and free form can coexist. Pick what fits instead of one template for every move.

Itemized vs free form inventory
Mode What it is When to use Who fills
ItemizedStructured lines, quantities, room or group patterns; can tie to a master catalog where you configure it.Accurate counts, warehouse heavy jobs, repeatable estimating.Estimator, warehouse, or customer self service via a shared link.
Free formFlexible or narrative capture without full line item structure.Smaller jobs, early qualification, or when a full count is not worth the friction.Estimator or customer, per how you run the job.

The job hub still shows what is in flight; document templates can pull inventory when you need paperwork that matches the list.

Interactive

Job inventory (staff)

Same staff inventory editor as the app (itemized or free form, rooms, import, Notes rail). Mock data only; unlock to try.

Demo note. Screens here will move as we ship. Treat them as a taste of how the fully functional product looks during alpha, not a promise that every pixel will match your own tenant on day one.

Notes

The same Notes panel everywhere

Notes is one panel everywhere (customer, job, other account views). On a job, new notes default to that job’s thread; on a customer, you see the full story with filters to narrow by job, person, or mentions, so crew, sales, dispatch, and the office are not retyping context in silos. @people and @groups route visibility; follow ups can notify, send scheduled email or text, or fire an automation, still on the same customer and job record.

Interactive

Notes

Toggle Job vs customer to see scope change; nothing is saved.

View as in the app

Job pages default to this job’s notes only, so the thread stays about the work order, crew, and schedule.

Notes

Notes linked to this job appear here. Use @people or @groups; tag Crew so this note can surface on crew job paperwork for move day.

Morgan Lee2h ago
Spoke to homeowner, third floor walk up, book elevator @Dispatch 8:00a slot. @Jordan FYI: they asked to loop you before we quote packing.
User Jordan Cole Group Dispatch
Confirm elevator with buildingDue Mon 4:00p
Jordan Cole Move day Yesterday
Thanks @Morgan. I’ll call them this afternoon. If we need a third crew member, I’ll @Crew when it’s set.
User Morgan Lee Group Crew
Pat Rivera Move day Mon
Access code 4521 for loading dock. Tagging @Crew for move day, narrow alley; tailgate in front not allowed.
Group Crew
Send payment reminder (template)Due Fri 9:00a

Demo note. Screens here will move as we ship. Treat them as a taste of how the fully functional product looks during alpha, not a promise that every pixel will match your own tenant on day one.

Reporting that stays honest as you grow

Reports draw from the same jobs, money, and activity your team already enters, scoped to your company, with saved views you can run again when the question comes back. Heavy workloads sit on analytics storage separate from the live ops path, so dashboards do not fight the rows your crews are editing.

Warehouse, when you need it

Storage and warehouse are optional per moving company. If you do not run a vault, MoveAnchor does not clutter the day with warehouse screens you will never use. When you do, you can follow goods from receiving through shipment groups and dispatch, align storage rates and billing periods the way your finance team expects, and give customers a portal view when it helps, without handing them the full back office. No separate warehouse add on: enable it on the same subscription when you are ready.

Access can be split so operations, billing, and the customer each see what they need: the floor sees movement, the office sees money and rules, and shared links stay under your control when you want to turn them off.

Capabilities at a glance

Operations

  • Sales stages you define, leads and opportunities
  • Customer accounts; jobs and lifecycle; dispatch and scheduling
  • Itemized or free form inventory; job and customer notes with mentions, routed to the right people
  • Tasks and reminders tied to the same data model as everything else

Communication

  • Templates and scheduled messages; company email and SMS from a provider, same patterns as the rest of the app
  • Visual automations: waits, branches, messages, and CRM updates on a canvas (integrations at capability level for your deployment)
  • Signable document builder and a branded shell for customer facing forms and document links, separate from staff chrome

Revenue

  • Invoices and recurring billing flows
  • PDF generation for documents that leave the building

Insights

  • Report builder with dimensions, metrics, filters, and allowed chart types: table, stat, bar, pie, line, area
  • Domains cover jobs, customers, invoices, messages, reminders, team activity, and, when applicable, claims, inventory, and warehouse events

Warehouse (optional)

  • Optional per customer: receiving, groups, dispatches, allocations, storage policies, periods, and customer shares you can revoke

Admin and security

  • The UI is driven from a large configuration surface
  • Access by role on the token, org admin, SSO patterns (e.g. OIDC), optional LDAP paths. Confirm for your environment.

And under the same roof

These areas still read from the same job and role rules. No extra login for each add on.

Reporting

Charts and tables off the same jobs, money, and message data you already entered. You are not forced to export to Excel before you can answer a question.

Warehouse

Receiving, dispatch, storage bills, and share links to the customer when you need them. The path stays off until you flip it on for that workspace.

Claims

A real file for a claim, with a place for photos and uploads when you want token links, instead of a thread nobody can find later.

Dispatch

Day board style views that sit on the job, not a pretty calendar with no link to the crew.

Fleet & accounting

We can meet fleet data where it already lives, and the accounting side follows the usual OAuth style sign in to QuickBooks style tools. We wire what you actually use, not a fake demo list.

Mobile

It is a normal web app. You can add PWA or wrap it in a native shell for policy reasons. We are not here to bluff a fake App Store listing.

What “all in one” means here

A straight list you can skim on a call. Every line is something in the real app, not a vibe word we painted on a slide.

  • Each customer’s data stays separate in the product’s authorization model
  • Pipeline: stages, leads and opportunities, and jobs with a defined lifecycle in the product model
  • Dispatch and scheduling on the main surface of the app
  • Tasks and reminders tied to the same data model that feeds reporting
  • Email and text (for example company mail, SMS from a provider) as core areas of the product
  • Invoicing, recurring flows, and PDF output from backend task patterns
  • Accounting: patterns in the style of OAuth toward common systems. Confirm for your install.
  • Report builder: sources, dimensions, metrics, filters, and chart types (table, stat, bar, pie, line, area)
  • Runs that read from a registry, with optional time bucketing and lazy joins in the engine
  • Optional warehouse: receiving, storage policies, accrual style periods, customer shares (revocable tokens)
  • The client loads a large config contract from the server
  • RBAC on the token, org admin, OIDC and SSO patterns; OpenAPI and docs for API consumers

Trust

Dependable, without a computer science degree

MoveAnchor is for owners and operations staff who live in the real calendar: when the board is full and everyone is on their phone, the system still needs to make sense. You should not need database vocabulary to trust that what you entered today is what your crew sees on the road tomorrow.

We expect accountants, insurers, and IT folks to ask where data stops and starts, how billing lines up with accounting, and what happens when something goes wrong. Those questions deserve clear answers in normal language, backed by documentation, not a slide deck and a handshake.

  • Your data stays yours

    The architecture we are building gives each moving company its own space. That means no shared dirty spreadsheet with a dozen other brands, and your people only see what their job requires.

  • It runs where the day runs

    We are building MoveAnchor as a proper web app: truck cab, front desk, or at home. If someone can get online, they should be able to get to the job without a special install for every new phone.

  • A foundation you can hand to IT

    When your accountant, insurer, or IT lead asks how it ties together, the aim is a real, documented product, not a one off build that breaks the next time you add a second truck. Integrations and security are the kind of hard questions we are designing for from day one.

MoveAnchor
Join the alpha or book a walkthrough when the link is up.