Private organization modules

When your process is genuinely different

EPT can design and build a private nano module for a validated workflow that standard software does not handle well. It stays inside the same secure platform instead of becoming a disconnected application.

A private build is for a validated gap

EPT first checks whether nano CRM, optional Billing, or sensible configuration can support the work. Custom development is considered when the workflow cannot be handled well that way.

Understand the workflow

Clarify the people, information, decisions, exceptions, and result the process needs.

Agree the scope

Define the module, migration, delivery, and acceptance requirements before development.

Build inside nano

Give the organization a focused module using the same platform and sign-in as its other work.

Connected, secure, and available only to your organization

A private module remains part of nano. It uses the platform capabilities already supporting CRM and Billing.

  • One nano sign-in
  • Existing organization users
  • Roles and permissions
  • Audit logs
  • Notifications
  • Protected files
  • Secure tenant separation
  • Responsive browser access
R1 650 per organization / month

After completion and acceptance, the private module has no additional ongoing module fee and no per-user fee.

Development is quoted separately

Discovery, development, migration, and acceptance are scoped and quoted separately from the subscription. New development or material changes outside the agreed scope may also be quoted separately.

This is not a no-code app builder.
EPT designs and implements an agreed private workflow. Unbuilt general modules are not presented as products.

Tell us where the standard workflow stops fitting

Share the process, who uses it, and what your current spreadsheets or manual steps cannot handle well. Do not send passwords or banking credentials.