Custom software development · S 180°
The application your company needs, built to fit it.
Most companies run on a stack of subscriptions, each one built for somebody else's process. We design and build the system you actually need: one tool shaped to your work, owned by you, and kept running by the people who built it.
What is custom software development?
Custom software development is designing and building an application for one company's specific process rather than buying a generic product. Norwind builds web applications and internal tools for US companies, often replacing several SaaS subscriptions with one system the company owns, then keeps running it after launch.
Who it is for
You will recognise yourself, or you will not.
- Companies paying for five subscriptions that each do a third of the job
- Teams whose process lives in spreadsheets, email threads and a shared drive
- Businesses that have outgrown an off-the-shelf tool and now work around it
- Founders with a product to build and no engineering team to build it
What you get
What arrives, and what stays.
- A system designed from your process, not a template with your logo on it
- Web applications, internal tools, integrations and the infrastructure under them
- Code you own, in a repository you control, documented for whoever comes next
- The same team after launch: maintenance, changes and support
How it runs
Four steps. The card goes round once.
Every step ends with something you can see.
01 · Discovery
We sit with the people who do the work and map what the system has to do, what it has to talk to, and what it must never get wrong.
02 · Design
Screens and data model together, reviewed with you before a line of production code is written.
03 · Build
Short cycles, working software at the end of every one. You see the real thing, not slides.
04 · Run
We deploy it, monitor it and keep it current. The products we build for ourselves are held to the same bar.
How it is priced
Fixed-fee discovery, then per-cycle.
Norwind does not publish rate cards. Every price is written before work starts, after a short discovery, and is specific to the engagement. The first call is free.
Discovery is a fixed fee and ends in a written scope, a first design and an estimate. Builds are billed per two-week cycle, so a client can stop at the end of any cycle and keep everything produced so far.
- Code, repositories, cloud accounts and domains in the client's name from day one
- A written weekly note on client builds and a monthly review on retainers
- No lock-in: documentation and handover are part of every engagement
Questions
The ones we are asked first.
What do you build with?
Widely used tools: TypeScript, React and Next.js in the browser, Node services behind them, Postgres, and cloud infrastructure set up in accounts you own. Boring on purpose, so the next engineer can pick it up.
Who owns the code?
You do. It lives in your repository from the first commit, and the accounts it runs on are in your name.
Can you replace a tool we already pay for?
Usually. We start by mapping what your team actually uses in it, which is often a fraction of what you pay for, and build that part properly.
How long does it take?
It depends on the system. We give an estimate after discovery, when we know what it has to do, rather than guessing before.
Use cases
Where this service usually starts.
Other headings
Tell us what you
are building.
Or what is in the way. We will tell you plainly what it needs, whether that is us or not.
- 01A reply from a person
- 02A free half-hour call with an engineer
- 03A written answer: scope, rough cost, where to start
Replies come from a person, within two working days.