Polenist

Aerion Web Platform & AI SaaS

Authenticated Aerion web platform

Investor dashboard, wallet connection, ARN activation and an admin console — built behind the existing launch site.

Prepared by

Polenist

Prepared for

Aerion

v1.0 · July 2026 · Valid for 14 days

Scope

Exists
The public Aerion launch site. Marketing content only, no accounts, no wallet, no application logic.
Not built
Investor login, wallet connection, ARN activation, portfolio and vesting views, referral and campaign tooling, AI Operator cockpit, admin console.
This proposal
Design and build of that authenticated platform, delivered in 12 weeks.

Deliverables

Scope in numbers

screens

services

contract integrations

The price is based on this inventory. Every screen, service and contract read is listed in the detail pages of this proposal.

Contract integrations

  • Smart contracts are written and audited by a separate firm. Polenist integrates against them and does not author contract code.
  • 5–7 contract integrations are in scope, read-only.
  • Every contract-connected view is built against structured sample data first, then switched to live reads.
  • Aerion provides ABIs, deployed addresses and a test environment. Live reads are enabled after that handoff.
  • A late handoff shifts the integration window only. All other work continues on schedule.

Timeline

  1. Weeks 1–4

    Foundation, auth, wallet, activation flow

    Demo · week 4

  2. Weeks 5–8

    Dashboard core, campaigns, AI layer

    Demo · week 8

  3. Weeks 9–12

    Admin, exchange readiness, QA & handover

    Handover · week 12

12 weeks total, three milestones. Demos at weeks 4, 8 and 12. Week 12 is handover.

/delivery

Schedule scenarios

Scenario A

Contract handoff on time

If the contract handoff, provider selections and content arrive as planned, the platform ships in week 12 with live contract reads. This is the baseline plan.

Scenario B

Contract handoff late

If the handoff is late, all views are completed with structured sample data and delivered in week 12. Live reads are enabled when the handoff arrives. The integration window shifts by the length of the delay; no other item moves.

Scenario C

Providers or content undecided

If the KYC or payment provider is not selected, or legal texts and translations are not delivered, the platform ships with marked placeholder flows and a single language. Those integrations are handled as follow-up work after the decision.

Price & payment terms

20,000 USDT + 3,000 USDT in ARN

Payment
Two equal instalments: 10,000 USDT on signature, 10,000 USDT on delivery.
Token
Vesting agreed in writing at signature. The token portion is renegotiated in good faith if the token launch is cancelled or materially delayed.
Maintenance
First 3 months after launch included. Updates and technical maintenance thereafter at 400 USDT per month; new features quoted separately.

Open items

Eight items require an answer from Aerion before kickoff; they set the final dates and the live-data scope.

  1. 01Contract handoff date (ABIs, addresses, test environment)
  2. 02Automatic timeline shift if handoff is delayed
  3. 03Sample-data delivery accepted as completion
  4. 04KYC & payment provider selection
  5. 05Legal texts provided by Aerion
  6. 06Translations provided by Aerion
  7. 07Product design: provided or by Polenist
  8. 08Post-launch maintenance agreement

Next steps

  1. 01Review this proposal and the six detail pages.
  2. 02Answer the eight open items.
  3. 03Sign and set the kickoff date.

Valid until [date] · hello@polen.ist