Assembled Systems — Terms of Service

Last Updated: January 2026

Provider: Assembled Systems

Client: The individual or entity entering into this Agreement

These Terms of Service ("Agreement") govern the software development subscription provided by Assembled Systems ("Provider"). By signing, paying, or otherwise engaging the service, the Client agrees to the following terms.

1. Service Model

Assembled Systems operates as a subscription-based development team, providing continuous engineering work on a monthly basis.

The goal is consistent, ongoing delivery of features, improvements, and product progress every month.

This model is built on:

  • Continuous engineering work
  • Monthly tangible progress
  • Flexible prioritization
  • No fixed scope
  • No penalties for changing requirements

You are not purchasing deadlines — you are purchasing ongoing development momentum.

2. Scope of Services

2.1 Included Services

Provider will supply a dedicated engineering pod that may include:

  • Full-stack development
  • QA testing
  • Bug fixes and maintenance
  • Architecture and planning
  • DevOps & deployment assistance
  • Sprint planning & backlog refinement
  • Monthly progress summaries
  • Ongoing communication via agreed channels

2.2 No Deadline Commitments

Provider does not commit to:

  • Specific delivery dates
  • Milestone deadlines
  • Launch timelines
  • Fixed-scope deliverables

All work is performed on a continuous-delivery basis, aligned with the monthly subscription model.

2.3 Monthly Deliverables

Each month, Client will receive tangible work output such as:

  • Completed features
  • Pull requests
  • Accepted code changes
  • Deployment updates
  • Demonstrations of monthly progress
  • Updated roadmap visibility

Work delivered is proportional to the capacity of the subscribed engineering pod.

3. Prioritization & Flexibility

3.1 Client Priority Control

Client may adjust feature priorities, backlog items, and direction at any time.

3.2 No Penalty for Scope Changes

Provider does not charge for:

  • New requirements
  • Feature swaps
  • Reprioritization
  • Adjusted direction
  • Updated scope

Work is always executed based on the highest priority items identified by the Client.

4. Payment Terms

4.1 Subscription Billing

This service is billed as a recurring monthly subscription.

4.2 Initial Payment & Start Date

  • The first month's payment is due upon signing.
  • The date payment is received becomes the Service Start Date.
  • The Start Date also becomes the recurring monthly billing date.

4.3 Monthly Fees

Fees are determined by the selected subscription tier outlined in the Client's proposal or invoice.

4.4 Automatic Renewal

The subscription automatically renews each month unless terminated under Section 5.

4.5 Non-Payment

If payment is not received within 5 business days of the billing date:

  • Provider may pause all development work
  • Paused time does not create refunds, credits, or extensions

Service resumes once payment is resolved.

5. Term & Termination

5.1 Term

This Agreement is month-to-month.

5.2 Client Termination

Client may terminate by providing 30 days' written notice via email.

Billing and service continue throughout the 30-day notice period.

5.3 Provider Termination

Provider may terminate this Agreement for any reason with 30 days' written notice.

5.4 No Refunds

All payments are non-refundable, including partial months or unused time.

6. Intellectual Property

6.1 Client Ownership

Client owns all intellectual property created during the engagement, including:

  • Source code
  • Repositories
  • Designs
  • Documentation
  • Infrastructure and deployments

6.2 Access

Client will maintain ownership and administrative access to all systems, including:

  • GitHub or source control
  • Cloud environments (AWS, GCP, etc.)
  • Databases
  • Project management tools

Provider does not retain ownership over Client assets.

7. Communication & Reporting

Provider will provide:

  • Ongoing communication via designated channels (e.g., Slack)
  • Weekly planning or check-ins
  • Monthly delivery summary
  • Roadmap updates as needed

Communication cadence may be adjusted based on mutual agreement.

8. Limitations & Disclaimers

8.1 No Guaranteed Outcomes

Provider does not guarantee:

  • Delivery by specific dates
  • Project completion timelines
  • Business outcomes
  • Performance metrics
  • Success of third-party integrations

8.2 Client Dependencies

Delays caused by Client inaction, missing information, third-party vendors, or environment issues may slow progress. Provider is not responsible for such delays.

8.3 Capacity

Monthly output is limited to the engineering capacity associated with the selected subscription tier.

9. Confidentiality

Both parties agree to maintain confidentiality regarding:

  • Business information
  • Technical assets
  • Product concepts
  • Code
  • Credentials
  • Communication

This obligation remains in effect even after termination.

10. Limitation of Liability

To the fullest extent permitted by law:

  • Provider's liability is limited to the fees paid by the Client in the preceding 30 days.
  • Provider is not liable for indirect, consequential, punitive, or special damages.

11. Governing Law

This Agreement is governed by the laws of the state in which Assembled Systems is headquartered, unless otherwise stated in a signed contract.

12. Acceptance

By signing a proposal or agreement, submitting payment, or otherwise engaging the service, the Client confirms acceptance of these Terms of Service.

Addendum Section

The following terms apply only to Clients who purchase the Flow Pod subscription.

13. Flow Pod-Specific Terms

The following terms apply exclusively to Clients subscribed to the Flow Pod. All other sections of this Agreement remain in effect unless explicitly modified below.

In the event of a conflict between these Flow Pod-specific terms and other sections of this Agreement, this Section 13 shall govern for Flow Pod services only.

13.1 Flow Pod Service Model

The Flow Pod is a queue-based, non-dedicated development service designed for:

  • Small development tasks
  • Experiments and proof-of-concepts
  • Internal tools
  • Early-stage application prototypes

The Flow Pod does not operate as a dedicated engineering pod and does not follow the same operating model, cadence, or level of collaboration as other Assembled Systems subscriptions.

Work is delivered sequentially from a shared development queue and is optimized for speed, learning, and validation, not long-term production use.

13.2 Prototype-Only Nature of Work

Any new application, system, or feature developed through the Flow Pod is considered a prototype unless otherwise agreed in writing.

Flow Pod deliverables:

  • Are not designed for scale
  • May rely on accelerated or experimental architectural patterns
  • May include AI-generated or AI-assisted code
  • Are not intended for production-grade, mission-critical, or high-availability use

Production readiness, scalability planning, performance optimization, security hardening, and long-term architecture are explicitly out of scope for the Flow Pod and require migration to a higher-tier subscription.

13.3 AI-Assisted Development

Client acknowledges and agrees that the Flow Pod leverages AI-assisted development tools as part of its delivery model.

As a result:

  • Code may be generated, modified, or accelerated using AI systems
  • Output may prioritize speed over polish or long-term maintainability
  • Manual refactoring may be required for production use

Provider makes no warranties regarding the originality, performance, or long-term suitability of AI-assisted output.

13.4 Scope & Delivery Mechanics

For Flow Pod subscribers:

  • Work is completed one task at a time
  • Tasks are processed in first-in, first-out order
  • No guarantees are made regarding turnaround time or monthly output
  • Unused capacity does not roll over

Flow Pod capacity is shared and variable and is not comparable to a dedicated engineering pod.

13.5 Communication & Meetings (Flow Pod)

The Flow Pod includes limited communication only, typically asynchronous.

The Flow Pod does not include:

  • Weekly or biweekly meetings
  • Monthly pulse checks
  • Sprint planning sessions
  • Demos or roadmap reviews
  • Ongoing product management

Any additional meetings or reporting are at Provider discretion and are not guaranteed.

13.6 Exclusions (Flow Pod)

The Flow Pod does not include:

  • Dedicated engineers or teams
  • Product strategy or roadmap ownership
  • SLA commitments
  • Performance, load, or security testing
  • Compliance work (HIPAA, SOC 2, etc.)
  • Business-critical system development

If work exceeds the intended scope of the Flow Pod, Provider may recommend upgrading to another subscription tier.

13.7 No Production Reliance

Client agrees not to rely on Flow Pod deliverables for:

  • Revenue-critical systems
  • Customer-facing production software
  • Regulated or compliance-heavy environments
  • High-availability or fault-tolerant systems

Provider shall not be liable for damages arising from production use of Flow Pod deliverables.

13.8 Upgrade Path

Flow Pod Clients may upgrade to another Assembled Systems subscription at any time. Any prior Flow Pod work may require refactoring or rebuild under the upgraded service.

Addendum Section

The following terms apply only to Clients who purchase Business Intelligence, The Core, or The Momentum subscriptions.

14. Business Intelligence Subscription Terms

The following terms apply exclusively to Clients subscribed to Assembled Systems' Business Intelligence ("BI") services.

In the event of a conflict between these BI-specific terms and other sections of this Agreement, this Section 14 shall govern for Business Intelligence services only.

14.1 Business Intelligence Service Model

The Business Intelligence subscription provides ongoing data analysis, reporting, and dashboard development services on a monthly subscription basis.

The BI service may include:

  • Data ingestion and integration from Client systems
  • Data modeling and transformation
  • Dashboard creation and maintenance
  • Custom reporting and analytics
  • KPI definition and metric tracking
  • Ad-hoc data analysis and insights
  • Ongoing dashboard updates and refinements

BI services are advisory and analytical in nature and do not constitute business, financial, accounting, legal, or investment advice.

14.2 No Guaranteed Insights or Outcomes

Provider does not guarantee:

  • Specific business outcomes or performance improvements
  • Revenue growth or cost reduction
  • Accuracy of third-party data sources
  • Completeness of Client-provided data

Insights are derived from available data and assumptions and should be used as decision-support tools only.

14.3 Client Data Responsibility

Client is responsible for:

  • Providing accurate and timely access to data sources
  • Ensuring data integrity and correctness
  • Maintaining required permissions and credentials

Provider is not responsible for inaccuracies resulting from incomplete, outdated, or incorrect data.

14.4 Dashboard Evolution

Dashboards and reports may evolve over time based on:

  • Changing business questions
  • New data sources
  • Metric refinements
  • Updated priorities

Historical dashboards may be modified or deprecated as part of ongoing optimization.

14.5 Tooling & Platforms

Provider may utilize third-party tools, platforms, or visualization software. Provider does not guarantee the availability, uptime, or continued operation of any third-party tools.

14.6 No Real-Time or SLA Commitments

Business Intelligence services do not include:

  • Real-time monitoring guarantees
  • SLA-backed response times
  • Incident response or alerting unless explicitly agreed in writing

14.7 Intellectual Property (BI)

Client retains ownership of:

  • Dashboards
  • Reports
  • Data models created specifically for Client

Provider retains ownership of any proprietary frameworks, templates, methodologies, or internal tooling used to deliver BI services.

15. The Core Subscription Terms

The following terms apply exclusively to Clients subscribed to The Core plan.

In the event of a conflict between these Core-specific terms and other sections of this Agreement, this Section 15 shall govern for The Core services only.

15.1 The Core Service Model

The Core is a dedicated engineering pod designed for:

  • MVP development
  • Early-stage products
  • New application builds
  • Foundational platforms

The Core provides a consistent monthly engineering capacity focused on building, validating, and iterating on a product.

15.2 Production Readiness

While The Core may produce production-capable software, the primary goal is functional progress and validation, not enterprise-grade scale by default.

Advanced requirements such as:

  • High availability
  • Advanced security hardening
  • Compliance (HIPAA, SOC 2, etc.)
  • Load testing at scale

May require additional scope or migration to The Momentum tier.

15.3 Dedicated Pod Structure

The Core includes a stable pod composition, which may include:

  • Developers
  • QA resources
  • Technical oversight

Specific staffing composition may evolve over time while maintaining equivalent capacity.

15.4 Capacity & Throughput

Monthly output is limited by:

  • Pod capacity
  • Technical complexity
  • Client responsiveness

Unused capacity does not roll over.

16. The Momentum Subscription Terms

The following terms apply exclusively to Clients subscribed to The Momentum plan.

In the event of a conflict between these Momentum-specific terms and other sections of this Agreement, this Section 16 shall govern for The Momentum services only.

16.1 The Momentum Service Model

The Momentum plan is designed for existing products and revenue-generating software that require:

  • Ongoing feature expansion
  • Performance improvements
  • Technical debt reduction
  • Scalability planning
  • Operational stability

Momentum prioritizes reliability, sustainability, and long-term product health.

16.2 Production & Business-Critical Systems

The Momentum tier is suitable for:

  • Customer-facing systems
  • Revenue-impacting workflows
  • Operationally critical applications

However, Provider still makes no guarantees regarding uptime, revenue impact, or business outcomes.

16.3 Expanded Engineering Focus

Momentum work may include:

  • Refactoring and optimization
  • Architecture improvements
  • Performance tuning
  • Reliability enhancements
  • Advanced testing strategies

Specific outcomes depend on prioritization and available monthly capacity.

16.4 Client Operational Responsibility

Client remains responsible for:

  • Hosting and infrastructure costs
  • Production monitoring and alerts unless otherwise agreed
  • Regulatory compliance obligations

Provider supports engineering execution but does not assume operational ownership unless explicitly contracted.

17. Subscription Tier Transitions

Clients may upgrade or downgrade between Business Intelligence, Flow Pod, The Core, and The Momentum subscriptions with written notice.

  • Changes take effect at the next billing cycle
  • Prior work may require refactoring or adjustment under a new service model
  • No credits or refunds apply for partial months