hehe.software

For founders, companies, and agencies

Web app development for a SaaS MVP or portal

hehe.software offers web app development for SaaS MVPs, customer portals and internal tools, including features beside your existing developer. We work remotely from Vancouver with businesses and agencies across Canada and the United States, including on products we did not build. Email mwe@hehe.software or use the contact form with what you need; a defined sub-project, white-label or credited, is welcome.

Email us

Web apps & MVPs, properly.

Custom builds and the platforms you already use.

01

What the first version includes

A web application means accounts, data that survives a refresh, and screens that finish a job. A brochure is a website, and we will say so if that is what you need.

SaaS MVP development is what a new person can finish: an account, one workflow, payment if you charge, and a staff view so support does not open the database. A customer portal shows that person's orders, files, or requests. Internal tools replace a spreadsheet with validation, permissions, and an export. Settings, a second product, and a phone app wait.

02

Typical jobs

Work we can quote names the tasks. Sign-up, sign-in, a password reset, an invite, and two roles. Create a record, edit it, share it, and mark it done. State a clear failure when a payment is declined. Include single sign-on only when the company already requires it.

A portal account must not see another customer's rows, a leak we also fix on apps we did not build. An internal tool usually imports the sheet, then enforces rules the sheet lacked. A custom web application can front an API or a payment provider you already run. We read a half-finished repository before proposing a rewrite. Where you ask for accessibility, we implement the technical side of WCAG on these screens: keyboard, names, focus, and contrast. We do not certify compliance.

03

From the first email to handoff

Tell us who signs in, what they must finish, what exists, and any real date. A clear workflow is a fixed quote, a bug is hourly, and a request that only says "a platform" is paid discovery. You can stop after the screen list, the roles, and the exclusions, and you keep that document.

You accept the build by using a preview, empty and failed cases included. You keep the repository, the domain, hosting, and the vendor accounts. Handoff says how to add a user, where the data lives, what a new environment needs, and what not to edit on the live app. Few projects run at once, so you reach the person writing the code.

04

Next.js, React, and TypeScript

The code is Next.js, React, and TypeScript, readable by a developer who joins later. UI/UX stays in the build when the flows are settled, and leads when they are not. Empty, loading, error, signed out, and a refused payment are part of the spec. A CRM, email, booking, a payment provider, or a webhook is attached only if launch needs it.

Swift and SwiftUI, Kotlin and Jetpack Compose, and React Native or Flutter are separate quotes. Apps we have released ourselves are on the App Store. This site is ours as well: a hand-built static site, with a WebGL hero, video, and structured data. It is not a SaaS product.

05

Who it suits

It suits a founder who will pick one job and drop the rest, a team leaving a spreadsheet or a shared inbox, and an agency that wants an MVP developer for a single piece, white-label or credited, beside a developer already there.

A brochure, a blog, or a store is scoped on its own. So is a promise of revenue, signups, or a search ranking, and any program that needs many people at once. The studio is in Vancouver, British Columbia, on Pacific Time, working remotely across Canada and the United States, with no second office.

06

What to send, and what we can show

Broski and ICD Atlas are examples of owned products that handle exact shares and offline reference data. Our portfolio also includes this hand-built website. They demonstrate implemented product behaviour in their actual platforms. For a web application, the agreed preview should demonstrate the requested workflow, saved data and access boundaries; the repository and release notes provide the implementation evidence.

Send the user, the job this version must do, and what done looks like. A sketch, API notes, or the sheet you want replaced speeds the quote. Account access can wait.

Ways to work with us

Built by us

We don’t show client logos. We show what we build and run ourselves — nine apps on the App Store, and this site.

Questions

Can you build one feature beside our existing developer?

Yes. A customer portal, reporting screen or integration can be scoped as a separate part of your application. We agree the data boundary, permissions, API contract and review process first. Your developer can continue to own the rest of the system.

What should a SaaS MVP scope contain?

Name the user, the task they must finish and the smallest workflow that supports it. Include access roles, saved data, error states and payments if the product charges. The estimate identifies backend work and release responsibilities rather than counting only visible screens.

Can you work with our developer or our agency?

An agency or a company can give us one piece, white-label or credited, while their own developer keeps the rest. We share the repository and agree who deploys before either side merges.

Do you stay on after launch?

Hourly covers a fix or a small change. A monthly retainer covers ongoing care, such as a broken screen, a new field, a dependency update, or a payment API that changed. We agree what it includes before it starts, including on apps we did not build.

How do quotes work?

Pricing is quote-only: we scope the job and send a fixed quote or an hourly estimate, and we publish neither a rate nor a package price. If the request names a category rather than a workflow, paid discovery comes first, and you keep that scope if you stop. Write to mwe@hehe.software or use the contact form.

Read first

Related services

Tell us what needs doing.

A short email is enough: what you have, what’s wrong or missing, and when you need it. We reply with questions or a plan.

mwe@hehe.software