Engagements & pricing
Every business has a different workflow, stack, data model, and operating constraint. I price the work around the problem being solved, while publishing starting points so you can decide whether Cwlwm Systems is in the right range before contacting me.
Project engagements
Most custom development engagements begin at $2,500. If the problem is not yet clear enough to scope responsibly, the fixed-price Systems & Workflow Review is designed to create that clarity first.
You receive a written proposal before paid development begins. The proposal and statement of work define final deliverables, phases, timeline, price, payment schedule, responsibilities, and any implementation or training work.
A defined operational problem that needs diagnosis before anyone starts building.
A focused workflow that can be improved by connecting systems or removing repetitive manual work.
A portal, dashboard, workflow, admin tool, or operational application built around how your business works.
A larger system spanning multiple workflows, users, data sources, integrations, and operational states.
Ongoing systems partnership
I can remain involved after a build to maintain the system, troubleshoot problems, onboard users, train teams, manage future phases, improve workflows, coordinate integrations, and keep the system aligned with the way the business is changing.
These are common retainer starting points rather than fixed service bundles. The actual agreement is based on system complexity, planned development, required availability, and how much recurring capacity should be reserved.
How ongoing partnership works →A live system that needs dependable maintenance, small changes, documentation updates, and a known person who already understands how it works.
A business with an active improvement roadmap that needs recurring development capacity in addition to maintenance and support.
A business that needs ongoing systems ownership, planning, development, and operational support without adding a full-time internal systems role.
A higher-touch relationship across several systems, locations, departments, or active initiatives where recurring capacity and continuity matter.
Phased builds
Larger platforms can be divided into useful phases so the business gets value earlier, validates the workflow in production, and makes later investment decisions with better information.
The exact phases depend on the dependency chain and business priorities, but a common pattern is foundation first, operating workflow next, intelligence after the data is trustworthy, and expansion after real use.
Establish the core data model, users, source of truth, and highest-value workflow so the business gets a usable first release instead of waiting for the entire roadmap.
Add integrations, automation, permissions, operational states, notifications, and the day-to-day workflows required to make the system dependable.
Layer in reporting, prioritization, management visibility, quality controls, and decision support once the operating data is trustworthy.
Extend the system to additional teams, locations, workflows, automations, or AI-assisted capabilities based on what the business has learned in production.
How pricing works
Custom work is quoted after the workflow, integrations, users, data, risks, and deliverables are understood well enough to write a responsible scope.
They show the level at which an engagement typically begins. Complexity, data quality, third-party APIs, migration, security, training, and change management can materially change the final scope.
Hosting, paid APIs, software licenses, messaging, email, maps, AI usage, or other vendor charges are identified separately when they apply.
Monthly partnerships are not unlimited work plans. The agreement defines the expected availability, recurring capacity, response expectations, what is included, and how additional work is handled.
Not sure what category fits?
I do not expect a client to arrive with a technical specification. If you can explain what is slow, manual, disconnected, hard to measure, or unnecessarily complicated — or what needs ongoing ownership after launch — that is enough to start a useful conversation.
Start with the problem
Describe the process, disconnected tools, reporting gap, repetitive work, handoff, or live system that needs ongoing ownership. I can help determine whether the right answer is a process change, integration, automation, custom system, phased build, or ongoing systems partnership.
Languages, frameworks, databases, cloud platforms, and development tools I use to design and build business systems.
