THE BUSINESS TOOLS MARKETPLACE

Run your business. Connect. Improve.

Find focused apps, portals, plugins, integrations, automations, AI assistants, templates and services for the work you need done. Explore a demo or a clearly defined planned scope, then choose the setup and support you need.

1,309individual product & service scopes

40core app demo entries

1269planned scopes · clearly marked

Missing your MicroERP?
Request it here

SHOP BY THE WORK YOU NEED

For Developers

Technical building blocks and source editions.

Documentation & product help

Find your next step

Confirm platform compatibility, required access and acceptance checks before requesting a build or service.

Product typeIndustryBusiness problemTarget platformDelivery formatPricing modelRequired integration

More filters

Business modelOriginal scope

Filters cover the whole catalogue. Listed platforms and integrations describe the intended scope; support must be confirmed before delivery. Pricing models describe the proposed offer, with charges agreed in its scope.

Choose the work

Shape it. Check it. Keep it.

Request a missing MicroERP or help quality check it. Both contributors get lifetime free access to that MicroERP after completion and quality approval.

Join as a quality reviewer

12 matching listings · 1 filter

Illustrative flow: Selected app architecture and agreed developer environment → Provide a documented starter edition with example modules and tests → Developers receive a scoped SaaS, admin-app or multi-tenant backend starting point.

Planned

Developer Products

Application Starter Kits

Developers receive a scoped SaaS, admin-app or multi-tenant backend starting point.

Across business types

SaaS starterAdmin app starterMulti-tenant backend starter

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Application foundation.

Proposed scope only. This listing is not an available app, download, connected integration or service booking. Deliverables, access, compatibility, price and acceptance checks must be agreed before delivery.

Input: Selected app architecture and agreed developer environment
Action: Provide a documented starter edition with example modules and tests
Outcome: Developers receive a scoped SaaS, admin-app or multi-tenant backend starting point.

Delivery format: Source code / SDK

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

SaaS starter
Admin app starter
Multi-tenant backend starter

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: Agreed NestJS contracts and data model → Provide selected module source, API contracts and integration examples → Developers receive the quoted catalog, booking, approval, notification or billing-adapter module scope.

Planned

Developer Products

Reusable NestJS Modules

Developers receive the quoted catalog, booking, approval, notification or billing-adapter module scope.

Across business types

Catalog moduleBooking moduleApproval module

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Reusable backend modules.

Input: Agreed NestJS contracts and data model
Action: Provide selected module source, API contracts and integration examples
Outcome: Developers receive the quoted catalog, booking, approval, notification or billing-adapter module scope.

Delivery format: Source code / SDK

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

Catalog module
Booking module
Approval module
Notifications module
Billing adapters

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: Selected provider/API contract and runtime → Provide a typed client SDK with documented errors and examples → The developer receives a scoped payments, document or integration client SDK.

Planned

Developer Products

Business SDKs

The developer receives a scoped payments, document or integration client SDK.

Across business types

Payments SDKDocument SDKIntegration client SDK

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: API client integration.

Input: Selected provider/API contract and runtime
Action: Provide a typed client SDK with documented errors and examples
Outcome: The developer receives a scoped payments, document or integration client SDK.

Delivery format: Source code / SDK, API / hosted service

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

Payments SDK
Document SDK
Integration client SDK

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: An agreed API request/response schema and sample inputs → Provide the selected endpoint contract and validation examples → A proposed document generation, structured extraction or notification API is scoped for integration.

Planned

Developer Products

API Products

A proposed document generation, structured extraction or notification API is scoped for integration.

Across business types

Document generation APIStructured extraction APINotification delivery API

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: API capabilities.

Input: An agreed API request/response schema and sample inputs
Action: Provide the selected endpoint contract and validation examples
Outcome: A proposed document generation, structured extraction or notification API is scoped for integration.

Delivery format: Source code / SDK, API / hosted service

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Usage charges: API pricing, quotas, authentication and provider costs are unconfirmed; no live endpoint or free usage allowance is advertised.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

Document generation API
Structured extraction API
Notification delivery API

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: Agreed frontend framework and accessible UI states → Provide selected component source with examples and integration guidance → The developer receives scoped data tables, workflow forms, booking calendars or product configurators.

Planned

Developer Products

Business UI Components

The developer receives scoped data tables, workflow forms, booking calendars or product configurators.

Across business types

Data tablesWorkflow formsBooking calendars

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Interface building blocks.

Input: Agreed frontend framework and accessible UI states
Action: Provide selected component source with examples and integration guidance
Outcome: The developer receives scoped data tables, workflow forms, booking calendars or product configurators.

Delivery format: Source code / SDK, Browser extension variant, Mobile companion variant, Desktop app variant, PWA variant, Kiosk interface variant

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.
Browser extension, mobile companion, desktop, PWA and kiosk editions are optional interface variants; each target and native integration is separately scoped, not a released build.

Data tables
Workflow forms
Booking calendars
Product configurators

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: Agreed role model and admin entity contracts → Provide source screens, state handling and documented data adapters → The developer receives user-management, settings, audit-view and operations-dashboard building blocks.

Planned

Developer Products

Admin Interface Kits

The developer receives user-management, settings, audit-view and operations-dashboard building blocks.

Across business types

User managementSettings screensAudit views

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Admin operations.

Input: Agreed role model and admin entity contracts
Action: Provide source screens, state handling and documented data adapters
Outcome: The developer receives user-management, settings, audit-view and operations-dashboard building blocks.

Delivery format: Source code / SDK

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

User management
Settings screens
Audit views
Operations dashboards

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: An allowlisted business API and authorised user context → Define permitted tool schemas, permission gates and server-side execution boundaries → Developers receive a proposed approved catalog, order, document or reporting tool adapter.

Planned

Developer Products

MCP Servers & Tool Adapters

Developers receive a proposed approved catalog, order, document or reporting tool adapter.

Across business types

Catalog toolsOrder toolsDocument tools

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Assistant tool access.

Input: An allowlisted business API and authorised user context
Action: Define permitted tool schemas, permission gates and server-side execution boundaries
Outcome: Developers receive a proposed approved catalog, order, document or reporting tool adapter.

Delivery format: Source code / SDK, API / hosted service

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

Catalog tools
Order tools
Document tools
Reporting tools

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: Agreed tools, allowed actions and acceptance examples → Provide tool definitions, execution flow and evaluation fixtures → Developers receive a workflow kit with bounded examples and reviewable execution outcomes.

Planned

Developer Products

Agent Workflow Kits

Developers receive a workflow kit with bounded examples and reviewable execution outcomes.

Across business types

Tool definitionsExecution flowEvaluations

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Agent execution design.

Input: Agreed tools, allowed actions and acceptance examples
Action: Provide tool definitions, execution flow and evaluation fixtures
Outcome: Developers receive a workflow kit with bounded examples and reviewable execution outcomes.

Delivery format: Source code / SDK

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

Tool definitions
Execution flow
Evaluations
Example inputs/outputs

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: Selected provider payloads and agreed delivery semantics → Provide receiver/import source, idempotency rules and retry examples → Developers receive a webhook receiver, import pipeline, retry queue or provider adapter starting point.

Planned

Developer Products

Integration Starters

Developers receive a webhook receiver, import pipeline, retry queue or provider adapter starting point.

Across business types

Webhook receiverImport pipelineRetry queue

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Reliable integration setup.

Input: Selected provider payloads and agreed delivery semantics
Action: Provide receiver/import source, idempotency rules and retry examples
Outcome: Developers receive a webhook receiver, import pipeline, retry queue or provider adapter starting point.

Delivery format: Source code / SDK

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

Webhook receiver
Import pipeline
Retry queue
Provider adapter

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: Agreed runtime, hosting target and environment contract → Provide environment templates, deployment scripts and monitoring setup instructions → Developers receive a reviewed deployment starting point without a live hosting promise.

Planned

Developer Products

Deployment Kits

Developers receive a reviewed deployment starting point without a live hosting promise.

Across business types

Environment configurationDeployment scriptsMonitoring setup

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Deployment configuration.

Input: Agreed runtime, hosting target and environment contract
Action: Provide environment templates, deployment scripts and monitoring setup instructions
Outcome: Developers receive a reviewed deployment starting point without a live hosting promise.

Delivery format: Source code / SDK

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

Environment configuration
Deployment scripts
Monitoring setup

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: Agreed API contracts and business workflow examples → Provide fixtures, contract-test examples and workflow acceptance scenarios → Developers receive reusable verification material for the selected integration scope.

Planned

Developer Products

Testing & Acceptance Packs

Developers receive reusable verification material for the selected integration scope.

Across business types

Contract-test examplesIntegration fixturesWorkflow acceptance scenarios

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Integration verification.

Input: Agreed API contracts and business workflow examples
Action: Provide fixtures, contract-test examples and workflow acceptance scenarios
Outcome: Developers receive reusable verification material for the selected integration scope.

Delivery format: Source code / SDK

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

Contract-test examples
Integration fixtures
Workflow acceptance scenarios

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

Illustrative flow: A selected product, agreed source boundary and licence requirements → Package the defined source files, build instructions and update terms → The buyer can review exactly what source, documentation, licence and updates are included.

Planned

Developer Products

Source-code Editions

The buyer can review exactly what source, documentation, licence and updates are included.

Across business types

Defined source packageBuild documentationLicence terms

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Source ownership scope.

Input: A selected product, agreed source boundary and licence requirements
Action: Package the defined source files, build instructions and update terms
Outcome: The buyer can review exactly what source, documentation, licence and updates are included.

Delivery format: Source code / SDK

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.

Defined source package
Build documentation
Licence terms
Update terms

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation

ONE CONNECTED E-COMMERCE JOURNEY

Build your e-commerce operating flow

Product choices, delivery slots, RFQ intake, returns, a store connector, setup and support in one proposed buying journey.

Proposed collection · 7 individual scopes

These are proposed scopes. Individual demos apply only where explicitly labelled. Platform permissions, deployment, configuration and ongoing support are agreed before delivery.

CHOOSE A CONNECTED STARTING POINT

Business bundles

Eight proposed packages group related listings around one business outcome. Their components are counted once in the catalogue above.

8 proposed packages

Planned bundle

Small Business Sales Pack

Capture an enquiry, assign ownership, approve a quote and organize follow-up.

Package scope & delivery

Proposed commercial composition of the referenced products. Components retain their own readiness and compatibility limits; setup, pricing and acceptance are quoted together. This bundle is not an additional software product.

Discuss this bundle

Planned bundle

E-commerce Operations Pack

Review orders, store stock, delivery choices and returns together.

Package scope & delivery

Discuss this bundle

Planned bundle

Training Business Pack

Connect batch/seat selection, registration, enrollment handoff and attendance administration.

Package scope & delivery

Discuss this bundle

Planned bundle

Agency Delivery Pack

Collect client inputs, approve scope and review delivery exceptions.

Package scope & delivery

Discuss this bundle

Planned bundle

Repair Business Pack

Use repair intake configuration, estimate approval and customer status updates.

Package scope & delivery

Discuss this bundle

Planned bundle

Wholesale Buying Pack

Offer an RFQ catalog, quantity pricing, orders and collections review.

Package scope & delivery

Discuss this bundle

Planned bundle

Subscription Business Pack

Scope plans, recurring orders, pause/skip requests and renewal reporting around the existing store.

Package scope & delivery

Discuss this bundle

Planned bundle

Field Service Pack

Collect service requests, assign work and record visit checks and customer sign-off.

Package scope & delivery

Discuss this bundle

BUILD WHAT YOUR BUSINESS NEEDS

Can’t find your MicroERP?

Request a new one and share the real workflow. Help us quality check it before release. The requester and quality reviewer receive lifetime free access to that MicroERP after completion and quality approval.

Request a MicroERP I want to help quality check

Demo entries link to central workspace access. Planned products, collections and services need agreed scope, development or configuration and acceptance checks. A listing does not certify integration availability, industry compliance or a granted licence.

Loading business tools and filters…

Planned

Developer Products

Business UI Components

The developer receives scoped data tables, workflow forms, booking calendars or product configurators.

Across business types

Data tablesWorkflow formsBooking calendars

One-time delivery, Scoped quoteproposed · scope and quote to confirm

View deliverables & requirements

For: Developers, technical teams and implementation partners

Business needs: Interface building blocks.

Input: Agreed frontend framework and accessible UI states
Action: Provide selected component source with examples and integration guidance
Outcome: The developer receives scoped data tables, workflow forms, booking calendars or product configurators.

Delivery format: Source code / SDK, Browser extension variant, Mobile companion variant, Desktop app variant, PWA variant, Kiosk interface variant

Pricing model: One-time delivery, Scoped quote. Proposed; availability, price and licence terms are agreed before delivery.

Approved data: Sample fixtures and explicitly authorised integration data only; this catalogue entry grants no source repository or production API access.

Read, draft & action scope: Implementation resource or API concept; production execution, credentials and deployment are excluded unless explicitly scoped.

Target platforms: Developer-selected runtime. Support must be confirmed for the selected version and permissions.

Compatibility & connection checks

Language/framework/runtime versions, provider API versions, dependencies and supported deployment targets are unconfirmed until the technical specification is agreed.
Source boundary, licence, redistribution rights, security responsibility, updates and support terms must be specified before delivery.
Browser extension, mobile companion, desktop, PWA and kiosk editions are optional interface variants; each target and native integration is separately scoped, not a released build.

Data tables
Workflow forms
Booking calendars
Product configurators

Support scope

Documentation and sample inputs/outputs for the quoted scope.
Implementation assistance, issue response and update coverage require explicit terms.

This is a proposed developer products scope. Availability, deliverables, dependencies, support and pricing are confirmed before delivery.

Discuss this scope

Documentation