liquidAPTS

Docs

Documentation for operators and partners.

The docs surface is organized around the real jobs this company site performs: qualifying requests, routing users, explaining upcoming product access, and supporting partner handoffs.

Business verification

Legal entity reference for reviewers.

This section separates the public liquidAPTS brand from the legal entity details used for D&B, Apple, app-store, banking, and enterprise verification workflows.

Legal entity name

LIQUIDAPTS

Registration style

M/s LiquidAPTS

Entity type

Partnership firm

Principal office

H. No. 849, Subhash Nagar, Near Shiv Mandir, Kasaridih, Durg, Chhattisgarh - 491001, India

Primary market

India

Use the legal entity name for D&B, Apple, app-store, banking, and enterprise verification workflows rather than product names or the public brand alone.
PAN, GST details if applicable, registration proof, address proof, telephone, authorized signatory details, employee count, and similar non-public verification fields should be supplied directly through authorized reviewer channels.

Product positioning

How the product positioning should work.

The public site should explain the current liquidAPTS catalog in business terms: an upcoming web platform for architecture firms and an upcoming association app for doctors.

Position aayamAi as an upcoming web platform for architecture businesses, covering projects, milestones, financials, staffing, procurement, and reporting in a browser-based workspace.
Position IMA as an upcoming mobile association app for doctors across locations in India, with communication, events, calendars, membership payments, conference collections, receipts, and reporting.

Pricing flexibility

Where monthly, annual, and AI credit pricing fit together.

The site should move users from curiosity into clarity: which product fits, what billing model makes sense, and how AI top-ups work when usage grows.

Pricing should show that liquidAPTS can fit different budgets and product adoption levels instead of forcing one rigid package.
Annual pricing should feel like a value path, not the only serious option.
AI credit top-ups should be presented as flexible usage expansion rather than a separate complicated product.

Access routing

Access flow documentation.

Product access is grouped by product and platform: web access for aayamAi, and mobile early access for IMA.

Upcoming web app

aayamAi

aayamAi is an upcoming web platform for architecture businesses, built around projects, staffing, financials, procurement, and reporting in one browser-based workspace.

Project delivery, staffing, and financial control in one web environment
Browser-based access for architecture teams planning an India-first rollout
Architecture-focused workflows without fragmented back-office tools
Contact us for accessRead access notes

Web

Web app

Upcoming web access path for architecture teams managing delivery, staffing, procurement, and commercial visibility from a browser.

Access: Guided web access

Status: Upcoming

Request this build

Upcoming mobile app

IMA

IMA is an upcoming mobile association app for doctor communities across locations, with communication, events, payments, receipts, and reporting in one flow.

Member communication and association updates in one app
Event publishing, payment collection, and receipt generation
Better administrative visibility across chapters and locations
Contact us for accessRead access notes

Mobile

iPhone / iOS

Planned iOS path for doctor members and association administrators handling announcements, events, and payment-related actions on iPhone.

Access: iOS early access request

Status: Upcoming

Request this build

Mobile

Android

Planned Android path for association communication, event coordination, collections, and receipt visibility on the go.

Access: Android early access request

Status: Upcoming

Request this build

Release visibility

Why the changelog and status pages matter.

Update notes and status signals are part of the product promise because they make upcoming rollout work legible before and after launch.

Use changelog tags to separate product work, access-flow changes, documentation updates, and release notes.
Keep releases chronological and attributable so visitors can tell what changed and why.
Use the status page for the public surfaces people actually depend on today: product access, docs, and contact routing.

Request handoffs

Access and contact reference

The public handoffs are intentionally compact, but they are still described clearly for operators and partners.

liquidAPTS handoff map

Lead capturePublic

Captures inbound contact signals so the company surface can qualify and route demand clearly.

Confirms the request was received and queued for review.

AccessPublic

Routes upcoming product access requests into the liquidAPTS contact flow with product and platform context.

Sends the visitor to the contact page with the right request context.

Handoff notes

  • Product access requests stay guided instead of exposing raw download links.
  • Contact requests keep enough context for the team to respond clearly.
  • Release notes stay readable for users, partners, and operators.

Partner handoffs

Patterns worth keeping simple.

Partner work is centered around a few reliable handoffs instead of a sprawling process.

Use the access handoff in product emails, onboarding flows, and device-targeted support messages.
Use the contact flow for inquiry capture when you need enough detail for follow-up.
Use docs and changelog pages as public visibility layers for launch communication and rollout guidance.

Shortcut reference

Keyboard shortcuts

The site includes a real command palette and go-to shortcuts to make the public experience feel product-grade.

Global actions

Open the global command paletteCmd/Ctrl + K
Jump directly to contactC
Jump directly to product accessD

Go-to navigation

Go to aayamAiG then A
Go to the Docs hubG then D
Go to IMAG then M

Brand assets

Brand asset distribution can be added here later.

This placeholder keeps the information architecture ready for brand marks, product visuals, and downloadable usage notes.