Step one
Scope
We work out what the thing actually is and write it down: what it does, what it explicitly does not do, what it runs on, what counts as finished, and what it costs. Nothing starts until that document is agreed and signed.
What we do
Two kinds of work, one kind of deliverable.
Your Hearth develops its own applications and takes on custom software builds for other people. Both end the same way, with software that runs.
To be plain about it: we are not consultants. There is no discovery retainer, no advisory deck, no strategy workshop, and no hourly rate for opinions. We are not a staffing agency and we do not place contractors inside your team.
We are hired to build a specific piece of software and to hand it over working. If what you need is advice rather than a build, we will say so and point you elsewhere.
Track one
Applications we develop in house.
We pick problems that are real, narrow, and badly served, then build for them properly rather than broadly.
-
—
Everyday friction
Planning, routine, and the small logistics that quietly cost people their week. The category is crowded with tools built for people who were already organized. We are interested in the other case: people who want to plan and have found that wanting to is not the hard part.
-
—
Places that run on volunteers
Community gardens, pantries, libraries, shelters, makerspaces, mutual aid groups. These places coordinate real work with a shared spreadsheet, a group chat, and somebody's memory, because the software built for shift scheduling is priced and shaped for businesses with a payroll department.
-
—
Privacy as a default, not a setting
Our applications are designed to keep data on the user's own device wherever a feature allows it. No advertising software, no third-party analytics, no session recording, no data sold or shared. This is a design constraint we accept up front, not a policy we bolt on at submission time.
Track two
Builds we take on for other people.
A defined piece of software, scoped in writing, built, tested, and handed over. Fixed shape, known end.
Step two
Build
We write it. You see working software early and often rather than status reports, and you talk directly to the person building it. If something in the scope turns out to be wrong, we raise it immediately instead of billing around it.
Step three
Hand over
You get the software, the source code, the accounts and credentials, and documentation written for a person. If you want us gone after that, you can run it without us. If you want us to keep maintaining it, that is a separate agreement.
What we take on
- Internal tools for work that is currently done by hand or in a spreadsheet nobody trusts anymore
- Applications for organizations too small or too specific for commercial software to fit
- Data work: getting records out of a system that will not export them, cleaning them up, putting them somewhere usable
- Finishing or rescuing a build that was started by someone else
- Apple platform applications, including App Store submission and release
What we decline
- Open-ended retainers and advisory arrangements
- Staff augmentation and contract placement
- Work whose scope cannot be written down before it starts
- Anything built to collect more personal data than its purpose needs
Nothing on this website is an offer, a quote, or a contract. Any engagement with Your Hearth LLC is governed solely by a separate signed written agreement. See our Terms of Use for the detail.
Next step
Describe the problem in a paragraph.
Who is stuck, what they do instead right now, and what would need to be true for the problem to be gone. That is enough for us to tell you whether this is a build worth doing.