liquidAPTS

Docs

Documentation for operators and partners.

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

Product positioning

How the product story should work.

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

Position InhouseAI as the operating system for architecture businesses, covering projects, milestones, financials, staffing, procurement, and reporting across web, desktop, and tablet.
Position IMA as the mobile association platform 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 device class: desktop and tablet for InhouseAI, and mobile for IMA.

Desktop + Tablet

InhouseAI

InhouseAI is delivered as a web-first operating system for architecture businesses, with desktop and tablet companions for teams managing projects, staffing, financials, and procurement.

Project delivery, staffing, and financial control in one environment
Desktop for deeper operating work and tablet for portable review
Architecture-focused workflows without fragmented back-office tools
Contact us for accessRead access notes

Desktop

Desktop

Primary operating build for architecture teams managing delivery, staffing, procurement, and commercial visibility from laptop and desktop surfaces.

Package: inhouseai-desktop.zip

Channel: Stable

Request this build

Tablet

Tablet

Tablet companion for portable review, project follow-up, and lightweight approvals away from the main desk workflow.

Package: inhouseai-tablet.apk

Channel: Stable

Request this build

Mobile

IMA

IMA is delivered as a mobile association platform 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

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

Package: ima-ios.ipa

Channel: Stable

Request this build

Mobile

Android

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

Package: ima-android.apk

Channel: Stable

Request this build

Release visibility

Why the changelog and status pages matter.

Release notes and status signals are part of the product promise because they make improvements legible after launch.

Use changelog tags to separate product work, access-flow changes, documentation updates, and release notes.
Keep releases chronological and attributable so customers 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 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 customers, 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 client-facing 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 InhouseAIG then H
Go to the Customers pageG then C
Go to the Docs hubG then D
Go to IMAG then M

Brand assets

Brand asset distribution can live here later.

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