Skip to content

Founder-led software for ordering, booking, payments, and admin systems

EDWORX LLC logoEDWORX

Agreements & Ownership

Agreements & Ownership

Plain-English overview of how EDWORX structures projects, support, IP, client data, and handoff options.

This page is a plain-English business summary. It does not replace the signed agreement packet. Final rights, responsibilities, pricing, support terms, and handoff terms are governed only by the signed agreement between EDWORX and the client.

Discuss your projectView pricing

The Simple Version

The standard EDWORX relationship in one paragraph.

EDWORX builds and supports configured software systems for clients. The client owns its business data, brand assets, content, customer records, and payment accounts. EDWORX owns its reusable code, templates, frameworks, workflows, and platform foundations. Standard projects include the right to use the deployed system for the client's own business. Source-code transfer, resale rights, exclusivity, or full ownership require a separate written buyout or transfer agreement.

This structure is designed to keep client operations portable while protecting the reusable foundations that allow EDWORX to build quickly and affordably.

The standard relationship

Clients are usually buying a configured supported system, not the full EDWORX platform.

  • EDWORX configures, customizes, launches, and supports a working software system for the client's business.
  • Standard projects include the right to use the deployed system for the client's own business operations.
  • EDWORX keeps its reusable platform foundations, templates, code libraries, workflows, and background IP.
  • The client keeps its brand assets, business content, customer records, and payment accounts.
  • Third-party services like Stripe, Square, Supabase, Vercel, domains, app stores, email, and SMS still operate under their own terms and fees.
  • If a client later wants broader handoff rights, source code, or ownership transfer, that is handled through a separate written agreement.

Ownership defaults

What EDWORX keeps, and what the client keeps.

The clean position is simple: EDWORX keeps the reusable system library and background IP, while the client keeps its own data, content, branding, and business accounts.

EDWORX frameworks, templates, source code foundations, and reusable components
EDWORX

These stay with EDWORX unless a later signed transfer agreement expressly identifies them as transferred assets.

EDWORX architecture, workflows, generalized improvements, prompts, scripts, and internal tools
EDWORX

The project does not assign EDWORX methods, know-how, or internal systems by default.

Client logos, photos, menus, pricing, policies, and brand content
Client

The business keeps ownership of its own materials and grants EDWORX only the license needed to perform the work.

Client customer, order, reservation, and operating data
Client

EDWORX may process that data as a service provider, but the data remains the client's.

Client payment processor accounts and business records
Client

EDWORX should help connect these accounts, not own the money flow or underlying client business records.

What this does not mean

This structure does not mean the client loses control of its business.

The client keeps its brand, content, customer data, order and reservation records, payment accounts, and business accounts. The structure only separates the client's business assets from EDWORX's reusable software foundations.

Account ownership

The best owner of each account depends on the asset, but client control is preferred for the business itself.

Domain registrar

Best owner: Client

EDWORX access: EDWORX gets delegate or DNS access as needed

The client should not feel hostage to its own domain.

Stripe or Square

Best owner: Client

EDWORX access: EDWORX gets admin or developer access during setup and support

The funds should flow directly to the client, not through EDWORX.

Hosting and database accounts

Best owner: Client preferred for larger clients; EDWORX-managed can work for simpler support plans

EDWORX access: EDWORX keeps technical access while support is active

The contract should say what happens to access if support ends.

GitHub or source repositories

Best owner: EDWORX by default

EDWORX access: Not transferred unless a buyout or source-code handoff is signed

This protects the reusable system library that makes EDWORX efficient.

App store accounts

Best owner: Client preferred

EDWORX access: EDWORX uses developer or admin access for build and maintenance

Transfers can be messy, so this is best decided early.

Email or SMS provider

Best owner: Client if used for customer messaging

EDWORX access: EDWORX gets technical access where needed

Client stays responsible for messaging content, consent, and provider compliance.

Payments, refunds, and taxes

EDWORX can support the integration, but it should not be treated as the merchant of record.

Payment processors such as Stripe or Square should generally be owned by the client. Funds, refunds, taxes, chargebacks, and payment-processor compliance remain the client's business responsibility unless a signed agreement says otherwise. EDWORX may help connect and support the technical integration, but EDWORX should not be treated as the merchant of record for the client's sales.

What is not included by default

Standard projects are built for your business to use the deployed system, not automatically transfer everything behind it.

If a client wants more than the standard production-use relationship, the next step is a separate written handoff, buyout, or transfer agreement.

  • Source code transfer
  • Resale or white-label rights
  • Sublicensing rights
  • Distribution rights
  • The right to create a competing platform from EDWORX retained IP

If monthly support ends

If support ends, the next step is handled through a defined transition path.

Standard monthly support keeps EDWORX responsible for hosting oversight, maintenance, bug fixes, small updates, and production support on the agreed system.

If support ends, the next step depends on the signed agreement and the handoff option selected. The goal is to make transition rights clear before a separation happens.

Depending on the agreement, support ending may lead to:

  • Data export
  • A short transition period or defined shutdown window
  • A production handoff license if that option is offered or purchased
  • A project-specific source-code buyout if a broader transfer is needed
  • A continued hosting-only or limited transition plan where available
  • Shutdown after notice if no ongoing support or handoff arrangement applies

EDWORX is not responsible for maintaining, updating, or troubleshooting unsupported systems unless a separate support or handoff agreement is in place.

Buyout & handoff options

If a client wants to leave, keep operating, or buy more rights, EDWORX uses a defined menu.

The buyout path is designed to make transition rights clear before a separation or transfer occurs. Different levels of handoff create different rights, different risks, and different pricing.

Option A: Data export only

Client gets: A reasonable export of client data and public business content.

EDWORX keeps: All code, platform IP, dashboards, infrastructure, and reusable systems.

Typical use: Best when a client simply wants to leave or switch vendors.

Option B: Production handoff license

Client gets: A perpetual or fixed-term right to keep using the deployed client instance without source code.

EDWORX keeps: Source code, templates, reusable platform rights, and the right to serve other clients.

Typical use: Best when the client wants continuity after support but does not need the codebase itself.

Option C: Project-specific source buyout

Client gets: Source code for the client-specific implementation, usually for internal use or a new vendor handoff.

EDWORX keeps: Background IP, generalized improvements, reusable modules, templates, know-how, and the right to build similar systems for others.

Typical use: Best when the client has an internal developer or outside technical team ready to take over.

Option D: Exclusive local-market license

Client gets: Narrow exclusivity in a defined geography, client segment, or industry lane.

EDWORX keeps: Underlying ownership and broader platform rights outside the purchased exclusivity scope.

Typical use: Best for a premium client that wants local protection without buying the full platform.

Option E: Full platform or IP acquisition

Client gets: A negotiated purchase of selected product-line assets, potentially including code, transfer rights, and future control.

EDWORX keeps: Anything not expressly included in the acquisition documents.

Typical use: Rare. This should be treated like an acquisition, not a normal client project.

After a buyout closes, EDWORX does not have an ongoing obligation to host, maintain, update, or troubleshoot transferred assets unless a separate post-closing support arrangement is purchased. Transition help, documentation, account transfers, and vendor handoff time are usually priced separately.

Attorney review note

This page is helpful context, but the signed agreement packet controls.

EDWORX should have a qualified attorney review larger contracts, source-code transfers, exclusivity requests, enterprise deals, and acquisition-style transactions before those terms are finalized.

This page remains a plain-English explainer. Final rights, obligations, support scope, pricing, and transfer terms come only from the signed agreement between EDWORX and the client.