WEB APPS & SAAS
Products your customers use
Multi-user web applications and SaaS products: accounts and permissions, billing hooks, dashboards, and the admin tools behind them.
Product design & development
Foundry 41 designs and builds web apps, MVPs, SaaS products, internal tools and integrations. Builds are scoped up front, you see working software every week, and the code lives in your repository.
Last updated
What we build
Software a business runs on: customer-facing web apps and SaaS products, first versions that need to reach real users, and the internal tools and integrations that hold operations together.
WEB APPS & SAAS
Multi-user web applications and SaaS products: accounts and permissions, billing hooks, dashboards, and the admin tools behind them.
MVPS
A narrow, well-built first release with the analytics and feedback loops to decide what comes next, instead of a prototype that has to be rewritten.
INTERNAL TOOLS
Admin panels, back-office workflows and reporting that replace spreadsheets and copy-paste between systems.
INTEGRATIONS
APIs, webhooks, data syncs and adapters between your product and the services it depends on, with retries, logging and reconciliation.
UX & UI DESIGN
User flows, wireframes and interface design, worked out with you and carried straight into the build.
Technology
By default: TypeScript end to end, React and Next.js for the interface, and AWS for hosting, data and infrastructure. One language across the stack keeps a small, senior team fast and keeps the codebase easy to hand over.
If your product already runs on something else, the scoped proposal says whether we work in it or recommend a change, and why.
How a build works
As a scoped build with weekly demos. The scope is written and agreed before paid work starts, you see working software every week, and the code is in your repository the whole time.
Step 1
A short call about the problem, the people involved, and whether we are the right team. No pitch deck.
Step 2
What will be built, in what order, what is out of scope, and how it will be accepted. Scope and fee are agreed before paid work starts.
Step 3
Working software every week, in your repository and your cloud account, so progress is something you can click on.
Step 4
Your team gets the code, documentation and runbook either way. A 30-day launch-defect warranty is included; Care or Care Plus is optional ongoing support, under access you can revoke.
Build & launch, then care
For a smaller, clearly agreed platform or MVP, we target about four calendar weeks from kickoff, including requirements, implementation, testing, deployment and handover. We confirm scope, capacity, access and client decisions before committing to a date; larger or more complex platforms need their own plan.
INCLUDED IN THE BUILD
Report defects against the agreed requirements within 30 calendar days of the agreed launch/acceptance date. We correct covered defects at no extra fee, even if the fix takes longer. This applies without a retainer; new features and later phases are separate.
OPTIONAL MONTHLY CARE
Up to 5 engineering hours per month for basic uptime/error monitoring, dependency and security maintenance, bug triage, fixes and small adjustments.
OPTIONAL MONTHLY CARE
Up to 10 engineering hours per month, with Care coverage, priority handling, small improvements and a monthly check-in on reliability and what to improve next.
Both plans provide next-business-day initial response during agreed support hours, not a guaranteed resolution time. Monitoring review, maintenance, investigation, fixes, review, testing, deployment and check-ins share the monthly allowance; covered warranty fixes do not. Monitoring coverage and cadence are agreed up front, not continuous human surveillance.
Unused hours do not roll over. Extra work needs written approval of its fee or scheduling in a later month; larger features get a separate quote. Hosting, model/API usage, third-party licenses and monitoring service bills are separate. No unlimited fixes, 24/7 coverage, or blanket security or compliance guarantee. Plan fee, supported systems, support hours, start date and cancellation terms are agreed before support starts.
Questions
Web apps, MVPs, SaaS products, internal tools and integrations between the systems a business already uses, including the UX and UI design.
By default TypeScript, React and Next.js, deployed on AWS. If your product already runs on a different stack, the scoped proposal says whether we work in it or recommend a change, and why.
As a scoped build with weekly demos. The scope is agreed in writing first; every week you see working software; changes to scope are agreed before they are built.
In your repository from the first commit, deployed to your cloud account. Rights to the code are set out in the agreement before work starts.
Yes. UX and UI design are part of the same engagement: flows, wireframes and interface design, then the build, by the same senior people.
Yes, as an assistant. Agents draft changes and open pull requests; checks and AI code review run on each change, and a senior engineer reviews every change before it merges.
For a smaller, clearly agreed release, we target about four calendar weeks from kickoff, including requirements, implementation, testing, deployment and handover. We confirm scope, capacity, access and client decisions before agreeing the date. Larger or more complex work needs its own delivery plan.
No. Scoped builds include handover and 30 calendar days after the agreed launch/acceptance date to report defects against the agreed requirements for correction at no extra fee, even if a covered fix takes longer. Care and Care Plus are optional, capped monthly plans; warranty fixes never consume their hours. New features are separate.
Bring the product idea or the codebase
Tell us what you are building, who it is for, and where it stands today. Initial scoping is free; we agree a build fee and delivery plan with requirements, testing and handover included. Monthly care is optional.