Sylent Systems
Packages and retainers
Published retainers make the first commitment visible. Parts, shipping, licenses, subscriptions, and work outside the written package remain separate.
Published pricing
Each package begins with a written agreement that confirms the delivery boundary, separately billed costs, timeline, and remaining payment schedule.
$500 retainer
Personal custom build
Parts and shipping billed separately
Component planning, assembly, validation, and handoff for a custom desktop or workstation matched to the intended workload and budget.
$2,000 retainer
Fleet and tenant setup
Hardware, shipping, licenses, and subscriptions billed separately
Fleet planning and onboarding for organizations that need consistent hardware, administrator boundaries, device ownership, and a documented rollout.
$2,000 retainer
Custom website
+ $200/month maintenance
Domain, hosting, paid services, and major new features billed separately
A responsive business website with clear content structure, accessibility and performance fundamentals, deployment, and a defined maintenance path.
Fleet and tenant intake
The fleet inquiry email is prefilled with the questions needed to understand the organization, devices, access model, integrations, deployment, and support boundary.
Email Fleet RequirementsAdditional packages
These services remain quote-based because integrations, access, risk, and validation requirements materially change the work.
Scoped estimate
Technical discovery
Recommended when the right implementation path is not yet clear
A focused review of the workflow, users, systems, access boundaries, risks, and acceptance criteria before committing to implementation.
Custom quote
Workflow automation
Quoted after the workflow and validation boundary are defined
A bounded automation or internal tool for repetitive handoffs, document processing, reporting, system integration, or review work.
Monthly retainer
Ongoing systems support
Scope and response expectations defined before service begins
Ongoing technical maintenance for approved websites, automations, infrastructure, or internal systems with explicit ownership and escalation boundaries.
Estimate basis
A useful estimate makes the cost drivers visible instead of hiding them inside a package name.
The number of user roles, decisions, exceptions, and handoffs the system must support.
The integrations, tenant permissions, APIs, legacy tools, and environment access required for delivery.
Sensitive-data boundaries, retention rules, identity controls, audit needs, and threat exposure.
The volume and condition of existing data, rollback requirements, backups, and reconciliation work.
The acceptance criteria, representative test cases, accessibility checks, performance targets, and release evidence required.
Documentation, training, deployment ownership, maintenance expectations, and post-launch response boundaries.
Every estimate includes
The proposal identifies the workflow, deliverables, assumptions, exclusions, dependencies, review points, acceptance criteria, timeline basis, and payment schedule.
Kept separate unless scoped
Software licenses, hosting, cloud usage, hardware, travel, taxes, and ongoing support are identified separately unless the agreement explicitly includes them.
FAQ
Clear answers help determine whether the workflow and engagement are a practical fit.
The retainer reserves project capacity and begins the planning, setup, or implementation described in the written agreement. The agreement states how the retainer is applied, the delivery boundary, and the remaining payment schedule.
No. Hardware, parts, shipping, taxes, licenses, subscriptions, and other third-party costs are billed separately unless a written agreement explicitly includes them.
The maintenance agreement defines routine technical care and an allowance for approved minor updates. Redesigns, new features, paid services, domain fees, hosting, and substantial content work are scoped separately.
Start with the organization, users, administrators, device count, locations, domain, current platforms, identity requirements, integrations, migration needs, security constraints, target date, and support expectations. Never send passwords or authentication codes.
A dependable quote requires a defined workflow, users, systems, access, deliverables, and validation boundary. Small, well-defined work may be quoted directly; uncertain work begins with technical discovery.
Start with the workflow
Describe the build, fleet, website, or workflow and the result it needs to produce.