Who is Liana Grigory?

Liana Grigory, also written Liana Grigoryan, is an entrepreneur, software engineer and United States Army veteran based in Los Angeles, California. She is the founder and chief executive of Grigoryan Capital Group LLC, the Wyoming holding company behind The Care Royal and Tegula Stone, and the founder of Unified Savers and DNL Bureau. She builds the products herself.

Is Liana Grigory the same person as Liana Grigoryan?

Yes. Grigory is the name she works and publishes under and the name her companies are registered against; Grigoryan is her birth name and still appears on her degree certificates and on LinkedIn. Both refer to the same founder in Los Angeles.

What does Liana Grigory build?

She founded The Care Royal, a multi-tenant platform for home care agencies; Tegula Stone, a two-sided marketplace for stone and tile contractors; Unified Savers, a non-profit informational resource for healthcare workers; DNL Bureau, a government contracting agency; and Grigoryan Capital Group LLC, the Wyoming holding company behind them.

How does Liana Grigory work with founders?

She takes equity instead of an invoice: nothing upfront, no retainer, no hourly, and nothing at all if the business does not work. She builds the product, the apps and the automation end to end. She works with US-registered businesses that already have revenue and a real market, and passes on pre-revenue ideas and on anyone who wants a pair of hands.

What technologies does Liana Grigory use?

TypeScript, React, Next.js, Node.js, Firebase including Firestore and Security Rules, Cloudflare Workers and Workers AI, Capacitor for native iOS and Android, Stripe, and Google Cloud. She writes about applying them at lianagrigory.com/publications.

How do you contact Liana Grigory?

Email info@lianagrigory.com, use the contact form at lianagrigory.com, or connect on LinkedIn.

LIANA GRIGORY

Los Angeles · I take equity, not invoices

You built the business. I’ll build the software. I only get paid if it works.

The business is real — customers, revenue, a market that wants the thing. It is being run on spreadsheets, group chats and somebody’s phone, and it is starting to come apart at exactly the point it started working. What would fix it is software nobody in the building can build, and the quotes come back at six figures.

I don’t write you a check. I build the thing the check was for. End to end — the product, the apps, the automation that should never have needed a person — and I take equity instead of an invoice. Nothing upfront, no retainer, no hourly. If the business does not work, I have worked for free, which is precisely why I am selective about whose business it is.

Liana Grigory — also written Liana Grigoryan. Three products have gone from an empty repository to a running business, two of them through App Store and Google Play review. I built all of them myself.

Selected work

The Care Royal Live · Web, iOS, Android

The Care Royal — onboarding in the live product

A multi-tenant platform that home care agencies run their day on: shift scheduling, caregiver and client records, applicant tracking, messaging and documents. Four roles — owner, manager, caregiver and family — each seeing a different product.

The work that matters most here is invisible: per-tenant isolation enforced at the database layer, so no agency can reach another's records even if the application code is wrong. Security that depends on the UI behaving is not security.

Caregivers clock in and out with GPS verification and the timesheet builds itself, then the platform computes gross, tax and net against current federal and California tables. Rather than depend on an external payroll provider, the calculation runs in-house — which removed the dependency and kept the platform out of the money-transmission path entirely.

Tegula Stone Live · Web, iOS, Android

tegulastone.com — contractor marketplace

A two-sided marketplace connecting homeowners with stone and tile contractors — quoting, bookings, messaging, reviews, and subscription billing driven by Stripe webhooks.

A production error-monitoring pipeline captures browser and backend faults, groups them by normalized signature, and alerts once per issue rather than once per occurrence — then does the less obvious half: filters out third-party scripts the business does not control. Most of the alerts were a bug in someone else's analytics beacon. An alert stream nobody reads is worse than none.

Instrumentation is only useful if it is honest. Edge counts and analytics were reconciled against each other before either was trusted, which caught a gap wide enough to have sent the roadmap the wrong way. Killing a conclusion beats defending it.

Unified Savers Live · Web

unifiedsavers.com — consumer product

A consumer savings product built on a serverless edge stack with static generation, holding a 90+ Lighthouse performance score across the site. Content architecture, technical SEO and the automated publishing pipeline are all owned in-house.

GCG Tools Live · Web

tools.grigoryancapitalgroup.com — small business and creator tools

Browser-based tools for small businesses: a paystub generator with current federal and state tax math and year-to-date totals, legal document templates such as NDAs, lien waivers and landlord forms, plus invoices, PDF tools and pay calculators.

For creators and service providers, Booking Pages gives each one their own editable booking page and a listing in a public directory. Documents are generated in the visitor’s browser, so their files never leave the device.

Shipped, not prototyped

Tegula Stone — live on the App Store

Two of these are native apps built, signed and pushed through App Store and Google Play review in-house — certificates, provisioning, store listings and all. Most products never survive that last mile.

Three examples, not the full list — an e-commerce storefront, an internal operations agent and several under wraps are not shown here.

Security & compliance

Products that hold health records, payment details and client addresses are built to be defensible from the first commit, not hardened after something goes wrong.

Isolation

Enforced below the application

Multi-tenant data separation written into database security rules, so one customer cannot reach another’s records even if the application code is wrong. A permission check that lives only in the interface is a suggestion, not a control.

Access control

Roles that cannot be self-granted

Role, tenant and permission fields are immutable to the account they belong to. A signed-in user editing their own record cannot promote themselves, because the rule pins those fields server-side.

Healthcare

Built to HIPAA’s technical safeguards

Care platforms are built against the HIPAA Security Rule’s technical requirements — unique user identification, role-based access, audit controls over record access, automatic logoff, and encryption in transit and at rest.

Review

Adversarial by default

Auth paths are reviewed as an attacker would: assume the client is hostile, assume storage is readable, assume the token is forged. That discipline has caught real privilege-escalation holes in production code before anyone else found them.

AI & automation

AI is used where it removes work that would otherwise need a person, and kept away from the parts that have to be exactly right. Every system below runs in production today, not as a demo.

Content at scale

Article generation on edge inference

A publishing pipeline that researches and drafts articles, running on Cloudflare Workers AI. It replaced a paid API that had quietly expired and stopped producing for five weeks. The replacement has no key to revoke and no per-article cost.

Autonomous operations

An operations agent that runs overnight

Every night it collects business data, scans six separate error sources, runs the SEO work, drafts marketing, then asks one question per business: what would win the next paying customer. The morning report is ready before the day starts.

Cost discipline

The right model for the job

Volume work — drafting, summarising, classifying — goes to a free tier. Judgement calls go to a stronger model. That split keeps inference cost near zero while the reasoning stays sound.

Guardrails

Deterministic where it counts

Audits count real faults in code; a model only prioritises and writes. Payroll maths is arithmetic against published tax tables, never inference. An AI that invents a problem is worse than no AI, so it never gets to decide what is true.

Approach

Shipping is the job

Code that is not in production has not been tested by anything that matters. Work goes all the way through review, signing, release and the monitoring that follows.

Measure before concluding

Numbers mislead more often than they lie. Every metric is reconciled against a second source before a plan is built on it, and the disagreement gets said out loud.

Leadership, not just delivery

A nineteen-person call centre operation, led to first place across the entire organization. Coordinating people is a separate skill from building systems, and a technical co-founder needs both.

Pitch me.

Tell me what the business is, what is breaking, and what you would give up to fix it. If it is a fit you get a call, and we talk about scope and what the split looks like. If it is not, you get a straight answer and the reason.

Your name (required) Company

Email (required) Phone for the call

What are you building? What stage are you at? Project details

Goes straight to Liana. No list, no newsletter.

By sending this you agree to the Terms of Use — which resolve disputes by individual arbitration — and to the Privacy Notice. Do not send confidential material before an NDA.

[email protected] Connect on LinkedIn →

About Liana Grigory · Speaking · Writing · Press kit

M.B.A., University of Hertfordshire · B.A. Psychology, American Military University

Add to Preferred Sources on Google