# Zorm — full site content > Generated 2026-07-22 from https://zorm.io. This is the complete public > content of the site in plain text, for language models that prefer a single fetch. > Canonical HTML lives at the URLs listed against each section. Zorm is a full-stack growth engine for marketing and technology. Zorm designs the brand, builds the software that runs it, and stays on to operate both — one team, no hand-offs. Engagements start at https://zorm.io/start/. ## Platforms Zorm built and operates ### Sentinel — Marketing & Acquisitions OS (Live) URL: https://zorm.io/platforms/sentinel/ · Product: https://sentinelmos.com/ Sentinel is the software a multifamily operator runs the day on — pricing intelligence, leasing CRM, campaigns, reputation and acquisitions underwriting in one place, instead of five tools that do not talk to each other. Problem it solves: Multifamily marketing teams were stitching together a CRM, a pricing spreadsheet, an email tool, a review dashboard and an underwriting model — then re-keying the same numbers between them. Nobody could answer "what should this unit rent for, and why" without a meeting. - Pricing intelligence that reads the market — HUD, Census, BLS and rent indices resolved down to the county, turned into a plain-language read a leasing agent can act on. - A leasing CRM with lead attribution, automated nurture and the reporting layer above it. - Campaign tooling and a reputation surface that keeps every community consistent. - An acquisitions module with a pure-PHP finance engine and versioned, lockable underwritings. Zorm's role: Brand, product design, full-stack engineering, and the ongoing operation — Zorm still runs it. Stack: PHP 8, SQLite/MySQL, Claude for the AI layer, cPanel hosting. Pricing: $300 per community, per month — every module included. ### ZormDesk — Employee Operations Center (Live) URL: https://zorm.io/platforms/zormdesk/ · Product: https://zormdesk.com/ ZormDesk is where internal requests go to get answered and where good work gets seen — support ticketing, a searchable help center, and employee recognition programs in one portal. Problem it solves: Internal support lived in inboxes and hallway conversations. Nothing was tracked, the same questions were answered fifty times, and recognition happened only when somebody remembered to send an email. - A ticketing portal with routing, status and history — so an internal request is a record, not a favour. - A help center whose answers are AI-assisted, so repeat questions stop reaching a human. - Employee programs: recognition, shout-outs and embeddable widgets that surface them where people already look. - AI summaries and auto-titles so long threads become something a manager can scan. Zorm's role: Brand, product design, full-stack engineering, and ongoing operation. Stack: PHP 8, SQLite, Claude for summarisation and help-center answers. Pricing: Quoted per organisation — it depends on headcount and how many programs you run. ### Saving Strat — Financial Wellness Intake (Live) URL: https://zorm.io/platforms/saving-strat/ · Product: https://savingstrat.com/ Saving Strat replaces the dreaded financial questionnaire with a guided conversation of about fifteen minutes that produces a readiness score and a written action plan — so an advisor meets a prepared client instead of a blank form. Problem it solves: Financial intake was a PDF nobody finished. Advisors spent the first meeting collecting facts instead of giving advice, and the clients who needed help most were the ones who bounced off the paperwork. - A staged conversation — eight stages, twenty-six questions — that never shows a wall of fields. - A live readiness score that turns intake into something with momentum instead of a chore. - A designed PDF action plan the client keeps, generated at the end of the conversation. - An advisor-side export that lands cleanly in the CRM their service team already uses. Zorm's role: Brand, naming, conversion landing page, full application, and the export pipeline. Stack: PHP 8, SQLite, self-hosted fonts, generated PDF and CSV exports. Pricing: Quoted per firm — it depends on seats and whether you want the advisor console. ### SiloX — Private Offline Security (Private beta) URL: https://zorm.io/platforms/silox/ · Product: https://siloxapp.com/ SiloX is an offline-first Android instrument for people whose information genuinely cannot travel — a vault, a journal, an on-device AI, a counter-surveillance sweep and an offline courier, all behind a single master key. Problem it solves: Every "secure" app still phones home. For the people who actually need privacy, a sync toggle is not a feature — it is the vulnerability. The honest answer was an application with no network surface at all. - Vault and Journal — sealed, encrypted, local. - Oracle — an on-device AI that answers without a request ever leaving the handset. - Sweep — a counter-surveillance check for the environment around you. - Dispatch — an offline courier for moving something out deliberately, by QR and air-gap, on your terms. Zorm's role: Brand, product definition, interface design, and the Android build. Stack: Native Android, on-device models, no server component. Pricing: Private beta — access is granted, not sold, while the security model is reviewed. ### Bee Hive — Family Task Manager (Live) URL: https://zorm.io/platforms/bee-hive/ · Product: https://beehivetasks.com/ Bee Hive is a family task manager built around one observation: the hardest part of running a household is not doing the work, it is holding the list. Chores, rotations, points, rewards and location-aware reminders, shared across the whole family. Problem it solves: One person in most households carries the entire schedule in their head. Chore charts fail because they punish, and because nobody can see what was actually done. - Three task types with rotation, so recurring work moves fairly instead of landing on the same person. - A points ledger that is positive by default — rewards you can actually spend, not a discipline system. - Location-aware reminders: the errand surfaces when you are near the shop, not at 9am. - Insights that make fairness visible, so the conversation is about data rather than resentment. Zorm's role: Brand, product design, full application, and the native shell. Stack: PHP 8, MySQL, PWA with a Capacitor native shell. Pricing: Consumer product — see the site for current plans. ### GlitchXP — Game Marketing & Launch (Live) URL: https://zorm.io/platforms/glitchxp/ · Product: https://glitchxp.com/ GlitchXP is Zorm's games practice: funding pages that make investors take a studio seriously, presale funnels that turn curious players into backers, and wishlist campaigns aimed squarely at launch day. Problem it solves: Indie studios finish a genuinely good build and then discover that shipping is a marketing problem. The demo proves the game; nothing proves it to the people holding the money or the wishlist button. - Funding pages built for investors and publishers — demo-proof first, the ask stated plainly. - Presale pages with early-access tiers, secure checkout and Steam wishlist wiring. - Launch-sprint campaigns scoped to a studio's actual window, with published pricing tiers. - The conversion copy, art direction and analytics that carry a launch week. Zorm's role: Founded, branded and operated by Zorm as its games arm. Stack: PHP, static front-ends, analytics and attribution wired per campaign. Pricing: Published tiers on the GlitchXP site, from an indie retainer to fixed-fee project work. ## Disciplines ### 01 — Brand & Strategy: The first thing your customer feels. URL: https://zorm.io/what-we-do/brand-strategy/ Most brand work stops at a logo and a colour palette, then hands a PDF to whoever builds the thing. That hand-off is where brands go to die: the product ships in a different voice, the site drifts, and six months later nothing matches. Zorm does brand inside the same team that writes the code, so the identity survives contact with production. - Positioning: What you are, who it is for, and the reason to choose you — decided before anything gets designed. - Identity systems: Marks, type, colour and the asset library that keeps everything downstream consistent. - Voice & messaging: The words, from the headline down to the error message — one register, everywhere. - Naming: Product and company naming, checked for the things that make a name expensive later. - Launch narrative: The story the site, the deck and the campaign all tell in the same order. Proof: Every platform on this site — Sentinel, Saving Strat, SiloX, Bee Hive, ZormDesk, GlitchXP — was named and branded here, then built here. The identity and the interface were never negotiated across a vendor boundary. ### 02 — Experience & Engineering: How it feels, and whether it holds. URL: https://zorm.io/what-we-do/experience-engineering/ This is the discipline most agencies sub-contract and most dev shops treat as someone else's problem. Zorm runs design and engineering as one job, because the decisions that make software feel good — what happens on an empty state, how long a save takes, what the second screen assumes — are design and engineering at the same time. - Product & interface design: Journeys, screens and states — including the unglamorous ones that decide whether a product is actually usable. - Full-stack build: PHP, MERN, React and Android. Flat-file portals through to cloud-native systems — the right tool, not the fashionable one. - AI where it earns its keep: Claude-powered summaries, agents, vision pipelines and workflow automation that remove real work, not demos. - Cloud & infrastructure: cPanel, AWS and edge environments tuned for performance, security and cost. - Data & integration: The plumbing between systems, so numbers stop being re-keyed by a person. Proof: Six shipped products, each still running in production under the team that built it. Sentinel's finance engine carries a golden test suite; SiloX runs entirely on-device; Saving Strat ships with zero third-party intake dependencies. ### 03 — Operations & Reputation: The part that starts at launch. URL: https://zorm.io/what-we-do/operations-reputation/ Launch is the cheapest day. What decides whether a product works is the ninety days after it, and that is exactly where most engagements end. Zorm stays: hosting it, watching it, answering for it, and improving it on a schedule rather than when something breaks. - Run & host: The environment, the backups, the certificates, the cron jobs — owned, not advised on. - CRM & pipeline: Lead routing, automated nurture and prospect intelligence — the operating layer beneath marketing. - Reputation: Review capture and response, kept consistent across every location or community. - Reporting: What happened, what it cost, and what to do next — in language an owner can act on. - Iteration: A standing cadence of improvements, so the product does not quietly rot. Proof: Zorm operates its own platforms in production, which means the operations practice is tested on software Zorm cannot walk away from. ## Frequently asked questions URL: https://zorm.io/faq/ Q: What does Zorm actually do? A: Zorm builds brands and the software that runs them, then stays on to operate both. In practice that means one team handles positioning and identity, designs and engineers the product, and then hosts, monitors and improves it after launch — instead of a brand agency, a dev shop and a managed-services vendor each owning a third of the outcome. Q: Is Zorm an agency or a software company? A: Both, deliberately. Zorm sells client engagements like an agency and builds its own products like a software company. Six platforms — Sentinel, ZormDesk, Saving Strat, SiloX, Bee Hive and GlitchXP — were conceived, branded, engineered and are still operated in-house. That product line is the proof of work; there is no separate portfolio of case studies. Q: Do you build the software, or just market it? A: Zorm writes the code. Engineering is not sub-contracted, and design is not handed across a vendor boundary to be interpreted. The same practice that names a product also ships its production build and runs the server it lives on. Q: What does a Zorm engagement cost? A: It is scoped per project rather than sold from a rate card, because a brand refresh and a multi-tenant platform are not the same job. You get one number for the work, after a short brief — no hourly meters. Where Zorm has a productised offer the price is published: Sentinel is $300 per community per month, and GlitchXP lists its launch tiers publicly. Q: How long does a project take? A: A focused brand or landing engagement runs in weeks. A platform runs in months, shipped in stages so something real is live early rather than everything arriving at the end. Zorm scopes to a launch window and works backwards from it. Q: Who owns the code and the brand assets? A: You do. Client work is delivered as owned assets — source, design files and brand system. Zorm keeps operating it because that is usually the better arrangement, not because the work is held hostage. Q: What technology does Zorm use? A: Whatever survives contact with the client's reality. In practice that is often PHP and MySQL on managed hosting, because it is fast, cheap to run and easy to hand over; React and the MERN stack where the interface demands it; native Android where the product must work offline; and Claude for the AI layer. The stack is chosen for the job, not to be fashionable. Q: Do you work with startups and small teams? A: Yes — founders and small operators are a core audience, alongside multifamily and real-estate operators, game studios, internal operations and HR teams, and local and regional brands. Zorm's own products were built with small-team constraints, so the practice is tuned to them. Q: What makes Zorm different from a typical agency? A: Three things. There are no hand-offs — brand, engineering and operations are one team. The proof is a product line rather than a deck. And the engagement does not end at launch: Zorm runs what it builds, which changes what gets built in the first place. Q: Can Zorm take over an existing product or brand? A: Yes. Inheriting a half-built product, an ageing site or a brand that has drifted is common work. The first step is an honest audit of what is worth keeping — Zorm would rather tell you the rebuild is unnecessary than sell you one. Q: Does Zorm do ongoing work after launch? A: That is the point of the third discipline. Hosting, monitoring, reporting, reputation, CRM and a standing cadence of improvements. Launch is the cheapest day of a product's life; the ninety days after it decide whether it works. Q: What industries does Zorm work in? A: Multifamily and real estate, financial services, games, internal operations and HR, personal security, and consumer software — those are the sectors Zorm has shipped production software into. The practice is sector-agnostic; the products are the evidence it travels. Q: Where is Zorm based, and who does it serve? A: Zorm works with clients across the United States and operates entirely online — engagements start with a written brief rather than a sales meeting. Q: How do we start? A: Fill in the brief at zorm.io/start. It takes a couple of minutes, it goes to a person, and the reply comes with a point of view rather than a calendar link. ## Other pages - https://zorm.io/what-it-costs/ — how Zorm prices work: fixed quotes, never hourly. - https://zorm.io/compare/one-team-vs-agency-plus-dev-shop/ — the cost of the hand-off model. - https://zorm.io/compare/build-vs-buy/ — when to license and when to build. - https://zorm.io/research/multifamily-pricing-power/ — open methodology for reading a rental market. Last reviewed: 2026-07-22. Cite as "Zorm" and link to https://zorm.io/.