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
Web apps, MVPs and SaaS products, designed and built.
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
What kinds of products does Foundry 41 design and 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.
MVPS
A first version that reaches real users
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
The tools behind operations
Admin panels, back-office workflows and reporting that replace spreadsheets and copy-paste between systems.
INTEGRATIONS
Systems that talk to each other
APIs, webhooks, data syncs and adapters between your product and the services it depends on, with retries, logging and reconciliation.
UX & UI DESIGN
Design by the people who build it
User flows, wireframes and interface design, worked out with you and carried straight into the build.
Technology
Which technologies does Foundry 41 use?
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.
- Language
- TypeScript
- Interface
- React and Next.js
- Cloud
- AWS, in your account
- Code
- Your repository, from the first commit
- AI assistance
- Agent-drafted pull requests, reviewed by a senior engineer before merge
How a build works
How does a product build with Foundry 41 run?
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
Fit call
A short call about the problem, the people involved, and whether we are the right team. No pitch deck.
Step 2
Scoped proposal
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
Build with weekly demos
Working software every week, in your repository and your cloud account, so progress is something you can click on.
Step 4
Hand over, or we operate
Your team takes over with the code, documentation, and runbook, or Foundry 41 keeps operating it under access you can revoke.
Questions
Frequently asked questions about product builds
What kinds of products does Foundry 41 build?
Web apps, MVPs, SaaS products, internal tools and integrations between the systems a business already uses, including the UX and UI design.
Which technologies do you use?
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.
How do you run a build?
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.
Where does the code live?
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.
Do you do design as well as development?
Yes. UX and UI design are part of the same engagement: flows, wireframes and interface design, then the build, by the same senior people.
Do you use AI to write code?
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.
Bring the product idea or the codebase
Start with a fit call.
Tell us what you are building, who it is for, and where it stands today. A short call decides whether a scoped build is the right next step.