Custom software development
Web applications, customer portals and internal systems, built around how your business works. We agree the scope and a fixed price first, then you use working software every week.
Four weeks of a fictional project: a request spreadsheet becomes an app.
| 12 Nov | Popescu | boiler noise | |
| 12 Nov | no hot water | Radu? | |
| 13 Nov | Ionescu | Radu | |
| 13 Nov | Ionescu | Radu |
- Popescu, Str. Lalelelor 4Boiler noiseNew
- Dumitru, Bd. Eroilor 12No hot waterAssigned
- Ionescu, Str. Morii 9Annual checkDone
Jobs per week
Released
- Today: one shared spreadsheet Requests typed in by whoever answers the phone. Blank cells, duplicates, no owner.
- Week 1: the request list Every request in one list with a status. You review: are these the right columns and statuses?
- Week 2: a form that refuses mistakes A new request cannot be saved without an address and a phone number. You review: the required fields.
- Week 3: technicians see their own jobs Roles and permissions. You review: who may see and change what.
- Week 4: the weekly report, released Jobs per week and open requests. You review: the report, then the release.
What changes
TodayThe business runs on spreadsheets and copied data.
With AL+One system, designed around how your people actually work.
TodayProjects drift and bills grow.
With AL+A written scope and one fixed price before any code.
TodayYou see the result only at the end.
With AL+Working software you try every week.
Web applications and internal systems
Products and portals
Customer-facing products, portals and subscriptions, released in stages.
Internal systems
Orders, scheduling, approvals and reporting that replace the spreadsheet.
The stack
Ruby on Rails, Elixir, Rust, PostgreSQL and native iOS, chosen for what you can maintain and hire for.
From scope to launch
The problem
Who uses it, what data it needs and your deadline. No specification needed.
Scope and fixed price
What it must do, what is left out and how we both check it.
Weekly builds
Each week ends with software you use. You pay weekly in advance, and either side can stop with one week's notice.
Handover or ongoing care
Code, tests and a runbook, or we stay on under maintenance.
Products built by AL+
PostDeploy Analytics installs into each user's own Cloudflare account. KeySend is a subscription product with daily jobs and generated client reports. We built both and run them.
Who this is for
A good fit
A system that matters enough to build and run, and someone on your side who decides every week.
Look elsewhere if
A product you can buy already does the job. Then buy it; we will tell you so.
Questions
Do I need a detailed brief?
No. Describe the problem and what you use today. We write the scope with you.
What does the fixed price include?
The work in the written scope. Hosting, paid services and support after launch are listed separately.
Who owns the code?
You do, in a code repository your company owns from the first commit. Open-source libraries and paid services keep their own licences.
Further reading
Software development outsourcing: decide who owns delivery
Choose what to outsource, compare development partners, and use a responsibility worksheet to agree acceptance, access, support, and exit before work starts.
MVP vs prototype: what should you build first?
Choose a prototype, proof of concept, or MVP by the question you need to answer. Use a decision table and a practical first-release brief.
Planning custom software development: scope and cost
Prepare a custom software development brief: users, workflows, integrations, scope, cost drivers, and acceptance checks before you ask for a proposal.
Web app vs mobile app: choose the first platform
Decide whether your first product needs a web app or a native mobile app. Compare user journeys, device needs, offline work, release scope, and ownership.
Discuss your software project
Tell us what the application needs to do and who will use it. We use that to define scope and prepare a quote.
Or copy the address: paul@alplustech.com