MRMEGSoftware practiceContact

How the practice works.

MRMEG is an independent software practice. Every engagement is scoped, designed, built, and supported by its principal, from the first call to launch.

Principles

  • One accountable lead

    The principal scopes, designs, builds, and supports every engagement. No account managers, no hand-offs.

  • Written scope, fixed price

    A written plan with timeline and price within 48 hours of the first call.

  • A working build every week

    Progress you can install, not a status report.

  • Continuity by design

    Code, store accounts, and cloud accounts are in your name from day one, with documentation another engineer could pick up.

Scope of practice

Apps for every screen
Phones, tablets, and desktops; watch apps, widgets, and extensions; and the web.
APIs and infrastructure
Data, auth, and deployment behind the product, built to be operated rather than just launched.
Rescues and rebuilds
Inherited codebases stabilized; MVPs re-architected for production.
Advisory
Architecture reviews, audits, and build-versus-buy decisions.

What you own

Code
In your name from day one
Store accounts
In your name from day one
Cloud accounts
In your name from day one
Documentation
Written so another engineer could pick up the work

The principal.

Leads every engagement, from scoping and architecture to the build itself. Maintains the practice’s open-source app toolkit, including @mrmeg/expo-ui.

Open source

Common questions

Who will I work with?
The practice’s principal, who scopes, designs, builds, and supports every engagement. There are no account managers and no hand-offs.
How is the price set?
It’s fixed in a written scope: a plan with timeline and price, within 48 hours of the first call.
Who owns the code and accounts?
You do. Code, store accounts, and cloud accounts are in your name from day one, with documentation another engineer could pick up.
Can MRMEG take over an existing app?
Yes. Inherited codebases are stabilized and MVPs re-architected for production; NeurospicyOS, an inherited MVP, is in progress now.
What happens after launch?
A 30‑day support window follows the production deployment, and the code and accounts are already in your name.
Which platforms?
Phones, tablets, desktops, watch apps, widgets, extensions, and the web, plus the APIs and infrastructure behind them: data, auth, and deployment.

Start with a conversation.

A 30‑minute call with the principal about goals, timeline, and budget. A written scope follows within 48 hours.

Book a call with the principal