Production and project workflow
Schedules, crew, locations, approvals and versions. The value is not the screens, it is writing down the rules that currently live in one coordinator's head before that person takes another job.
Los Angeles
Software development in Los Angeles the spreadsheet that runs the show.
Most LA software briefs start the same way: a production coordinator has a workbook nobody else can open, and the business now depends on it.
Overview
What LA software briefs look like
Custom software development in Los Angeles covers internal tools, web application development, customer portals and SaaS products. In this market the recurring brief is operational: production schedules, rights and usage windows, talent and roster management, or approvals that currently live in a spreadsheet only one person understands.
Rights, windows and usage
Who may use what, where, for how long. Almost every media adjacent business has this problem and almost all of them track it in a spreadsheet. It is genuinely complex logic and it is worth building properly.
Roster and talent management
Availability, rates, agreements, payments and reporting. Frequently the first system a growing agency or production company actually needs, and frequently the last thing anyone budgets for.
Web application development
Where the users are outside your organisation, a browser is usually enough. Web application development avoids installs, store review and two platform builds, and it is the right answer more often than clients expect.
Built for the next team
LA companies change suppliers often. Documented architecture, a stack with a wide hiring pool and no clever tricks means the next team inherits software rather than a mystery.
We will tell you not to build
If a configured platform already does it, if the rules are still being argued internally, or if nobody will maintain it. All three are common and all three are cheaper to hear before the build.
Pricing
What drives the cost
| Factor | Why it moves the number | What to ask |
|---|---|---|
| Rules nobody has written down | Discovery has to create them first | Who actually knows the process? |
| Rights and usage logic | Genuinely complex, and easy to get wrong | How many kinds of agreement? |
| Integrations | Each one is a project of its own | What connects, and what if it fails? |
| Roles and permissions | Who sees whose rates and terms | How many user types? |
| Data migration | Years of spreadsheets in varying shape | How clean is what exists? |
| Ongoing ownership | Someone maintains it or it rots | Who owns this in month twelve? |
We scope after a discovery engagement that produces a written specification you keep. Pricing custom software before the rules are documented gives a number that is wrong for both sides.
Detail
What to ask before you sign
| Ask them | A good answer sounds like | Walk away if |
|---|---|---|
| Who is actually writing this? | Named engineers, and what is subcontracted | The team you meet is the sales team |
| What documentation do we get? | Architecture, setup, deployment, as a deliverable | We will walk you through it |
| Could another firm take this over? | Any competent developer in that stack | Only we know how it works |
| Who owns the code and the repository? | You do, in your own account, from day one | Ownership ends when the retainer does |
In a market with this much turnover, the handover question matters more than the demo. Ask what the next team would need before you ask what this one can do.
Limits
When you should not build custom
A platform already does it
Standard project management, accounting, CRM or scheduling. Custom here means paying several times more for a solved problem and inheriting the maintenance.
The rules are still being argued
Building software freezes an internal argument into code. Settle it on paper first; changing a document costs a meeting and changing a system costs a project.
Nobody will maintain it
Custom software needs dependency updates, security patches and an accountable owner. Without one it ages faster and more dangerously than a platform.
FAQ
Common questions
When is custom software worth it for an LA company?
When the process is genuinely yours: rights windows, approval chains, roster rules or production workflows that no configured platform models. If the requirement is standard project management or accounting, a platform costs a fraction and is maintained for you.
Our process only exists in someone's head. Is that a problem?
It is the normal starting position and the first thing discovery fixes. We work through it with the people who actually run it and produce a specification in their language, usually the first time the whole rule set has existed in one place.
Can you build rights and usage tracking?
Yes, and it deserves proper treatment rather than another spreadsheet. Who may use what, where and for how long is real logic with real consequences when it is wrong, and it is worth the discovery time.
Should this be a web application or a mobile app?
Web application development where a browser is enough, which is most of the time. A mobile app is justified when repeat use, device capabilities or offline access genuinely matter to the work.
What if we change development partners later?
It should cost you a handover rather than a rebuild. Your repository, documented architecture, a stack with a wide hiring pool and no undocumented shortcuts. Ask any LA firm you shortlist what the next team would need.
How long does custom software take?
Three to nine months for a genuine application and longer for a product. An application quoted at four weeks is a platform configuration with a different name on it.
Can you take over software someone else built?
Often. We audit the stack, versions, code quality, documentation and dependency state first, then say honestly whether taking it over or rebuilding is better value. Sometimes it is genuinely rebuild.
Do you have an office in Los Angeles?
No. We work with LA companies remotely on Pacific hours and would rather say that than imply otherwise. Not carrying LA overheads is part of why our numbers differ.
Is web app development different from custom software?
It is the same discipline delivered through a browser. Web app development suits anything your customers or partners use, because there is no install and no version drift across machines. Internal tools sometimes justify a desktop or mobile client instead.
Next step
Tell us what you need.
Send us what you are trying to fix and we will tell you what it takes, what it costs, and whether we are the right people for it. If we are not, we will say so.