Independent software studio
Software you can hold us to.
We build web apps, AI agent workflows, cloud infrastructure, chatbots and SEO for growing businesses. Every project starts with a written scope and ends with you owning everything.
We reply within one business day.
Statement of work
Example
Customer portal and billing
- Prepared for
- Your company
- Scope
- Customer portal, Stripe billing, admin view
- Timeline
- 8 weeks, 4 milestones
- Price
- Fixed, agreed before work starts
- Demos
- Every Friday, on a staging link
- Ownership
- Code and accounts in your name
- Out of scope
- Anything not written on this page
For the client
For NexumLab
nex·um
noun, Latin. A binding obligation; the tie between two parties who have given their word.
We named the studio after it because the promise is the product. The code is how we keep it.
Services
Five services, one standard of work.
Most clients start with one and add another once the first has proven itself. Each is scoped, priced and delivered the same way.
Compare all services- 01Web app developmentCustomer portals, SaaS products, internal tools and dashboards.First release in 6 to 12 weeks
- 02AI agent workflowsAgents that read, decide and act inside the tools you already use.First workflow live in 4 to 8 weeks
- 03Cloud optimizationLower bills, calmer deploys and fewer late-night incidents.Audit in 2 weeks, changes over 2 to 6 more
- 04ChatbotsSupport and sales assistants grounded in your own content.Launch in 3 to 6 weeks
- 05SEOTechnical SEO and content that earns search traffic.Audit in 2 weeks, results compound over 3 to 6 months
The terms
Six promises we put in every contract.
Not a values page. These clauses go into the signed scope, so you can point at them if we ever fall short.
- §1
Scope in writing, before code
You get a written scope listing what we will build, what we will not, the milestones and the price. Nothing starts until you have signed it.
- §2
You own everything
Code, repositories, cloud accounts, domains and data sit in your name from the first day. There is nothing to hand back if we part ways.
- §3
Working software every week
Each week ends with something you can click, not a status update. You always know exactly where the project stands.
- §4
A reply within one business day
Emails are answered within one business day, during the project and after it.
- §5
Straight answers on fit
If a simpler tool, an off-the-shelf product or no build at all is the right answer, we will tell you, even when it means no project for us.
- §6
Thirty days of fixes after launch
If something we built breaks in the first thirty days after launch, we fix it at no extra cost.
Selected work
What changed for the people we built for.
Each study covers the situation before, what we built, and the measured result afterwards.
All case studiesCloud optimizationSoftware, 11 staffIllustrative
Cutting a SaaS startup's AWS bill by 41% with no downtime
Monthly AWS bill fell from $18,400 to $10,800 with zero production incidents
Read the case studyWeb app developmentHealthcare, 2 clinics, 18 staffIllustrative
Online booking cuts no-shows and phone time at a physio clinic
No-show rate fell from 19% to 9% within seven months of launch
Read the case studyStudies marked Illustrative use anonymized names and representative figures while client approval is pending.
Process
From first email to handover.
No discovery phase that ends in a slide deck. Each step produces something the next one depends on, and you can see all of it.
- Day 001
You email us
A few paragraphs on what you are building or fixing is plenty. No forms, no sales call to book.
- Within a week02
A short call
Thirty minutes on the problem, the constraints and the budget. We ask a lot of questions.
- A few days later03
Written scope
A fixed-price proposal with deliverables, milestones and an explicit list of what is out of scope.
- Weekly04
Build in the open
Demos every week, a shared board, and a staging link you can use whenever you like.
- Launch05
Full handover
Documentation, credentials and a recorded walkthrough, followed by thirty days of fixes.
Stack
Proven tools, chosen for the long run.
We favor widely used, well-documented technology, so your next engineer can pick up where we left off.
Web apps
- Next.js
- React
- TypeScript
- Node.js
- PostgreSQL
- Stripe
AI agents
- Python
- Anthropic
- LangChain
- n8n
- Supabase
- Redis
Cloud
- Docker
- Kubernetes
- Terraform
- Google Cloud
- Cloudflare
- Vercel
Chatbots
- Intercom
- HubSpot
- Shopify
SEO
- Search Console
- Analytics
- Semrush
- WordPress
Questions
Before you write to us.
Anything else, ask in your email. You will get an answer from an engineer, not a sales script.
How much does a project cost?
It depends on scope, which is why every price is fixed in writing before work starts. Audits are a fixed fee, builds are priced per milestone, and ongoing work runs on a monthly retainer. Include a rough budget in your email and we will tell you honestly what it can buy.
Who will I actually work with?
The people who scope your project are the people who build it. There is no account manager between you and the engineers.
Do I own the code?
Yes. Repositories, cloud accounts and domains are created in your name from the first day, and the code is yours when each milestone is paid.
Will you sign an NDA?
Yes. Send it with your first email, or ask us for ours.
Can you work with our existing team or codebase?
Often, yes. We start with a short review of the codebase so the scope reflects what is really there, rather than what we hope is there.
Why email and not a call booking link?
A written description of the problem makes the first call far more useful. We read every email and reply within one business day.
Start a project
Tell us what you are building or fixing.
hello@nexumlab.comInclude what you are building, your timeline and a rough budget. We reply within one business day. No forms, no chat widget, no sales sequence.