The account.
The identity.
The choice.
- Business number and domain
- Accounting organisation
- Payment account
- Marketing audience
- Account recovery
Permission to connect is specific to your agency.
Keep your accounts. Connect the work.
Posa’s model and talent agency software is designed to connect booking work with the accounts, sending identity and website your agency owns. Start with what needs to move, who checks it and where the final record belongs.
Agency identity stays with the agencyNorth Studio · example workspace
The account.
Posa’s planned role
Review the agency work.
Brief, people, dates, fees and the approved next step.
- 01Approved draft to accounting
Document and payment status back to the booking.
- 02Reviewed request to payments
Verified payment result back to accounts.
- 03Approved details to your website
A client enquiry back to the agency for review.
Chosen direction. Connections still to build.
Xero, QuickBooks Online, Resend and Stripe are selected providers, not connected services. WhatsApp, marketing, website publishing and file hosting also need their own implementation and agency setup. Saving a preference does not connect an account.
Available now
The standalone free comp-card maker works in your browser. It does not need a provider account.
Private preview
The staff workspace saves linked talent, client, enquiry, package and booking drafts. Wider workflows are design previews.
Before live use
Prove account permissions, reviewed actions, failure recovery and disconnection for the chosen agency. Setup, usage charges and service inclusions still need agreement.
Connect a purpose, not just a logo.
Choose a connection because it removes a specific piece of repeated work. These are the intended responsibilities and information flows.
01 · AccountsSelected · not connected
Xero or QuickBooks Online
Prepare an accounting handover from reviewed booking fees, rather than retyping an unreviewed estimate.
- Agency owns
- The accounting organisation and legal billing identity.
- Planned direction
- Approved invoice drafts out; issued document references, credits and payment status back.
- Check first
- Exact product, country, currency, tax mapping and accountant’s approval process. Agree an accountant export fallback where a connection is unsupported.
02 · Agency emailSelected · not connected
Resend
Use an agency-branded sender for reviewed messages, with replies finding their way to the right conversation.
- Agency owns
- The sending domain, visible identity and reply destination.
- Planned direction
- Approved messages out; delivery results and supported thread replies back.
- Check first
- Verify the agency’s sending domain and agree reply handling. Full Gmail or Microsoft mailbox synchronisation is a separate milestone.
03 · Client paymentsSelected · not connected
Stripe Connect
The intended model lets an independent agency collect client payments through its own connected account.
- Agency owns
- Its payment account and the client collection relationship.
- Planned direction
- Reviewed amount and currency to a hosted payment page; verified collection and refund status back.
- Check first
- Account eligibility, countries, currencies and fee responsibility. Stripe processing fees are separate from Posa’s payment fee; see launch pricing.
04 · Business messagingPlanned
Your agency’s WhatsApp number
Start with the agency’s business identity and actual needs for replies, mobile use and existing conversations.
- Agency owns
- The business account, number and account recovery.
- Planned direction
- Supported incoming messages to the right agency context; deliberately approved replies out.
- Check first
- The official provider route, number eligibility and any effect on existing app use or history. No automatic inbox, shared platform number or personal-session capture is supplied.
05 · MarketingPlanned
Your Mailchimp or Kit account
Keep the agency’s existing audience and campaign tools. Agree a narrow contact mapping before anything moves.
- Agency owns
- Its account, audience, sending identity and campaigns.
- Planned direction
- Reviewed eligible contact fields out; supported subscription and delivery changes back.
- Check first
- Audience, purpose, permission and unsubscribe handling. This is a design for a future connection, not live consent synchronisation. Campaign design and sending stay in the provider.
06 · Website and mediaPlanned
Approved public content
Connect an agency website to the details clients should see, while keeping original files and agency records private.
- Agency owns
- Its brand, domain and the decision about what may appear.
- Planned direction
- Approved boards, profiles and public media out; new enquiries back for staff review.
- Check first
- Private storage, media permission, publication and removal. The current tenant site is an unpublished shell. Explore the agency website plan.
One booking. Clear handovers.
A fictional Juniper studio campaign at the North Studio example workspace shows why each connection needs a defined job.
- Booker reviews the billing draft.
The talent, agreed fee, usage, legal issuer and currency need checking before accounts receives it.
- Accounts checks the accounting result.
In the planned flow, the accounting system returns the issued document reference. A saved Posa draft is not an issued invoice.
- Any deposit stays with that job.
A future payment request must use the reviewed amount. A client opening a payment page does not prove payment.
- A change has an owner.
If Juniper asks for a different date or usage, the booker reviews the change before new terms or billing instructions go out.
What if an account disconnects or the result is unclear?
The intended workflow stops affected actions and shows what needs attention. An uncertain payment or send must be checked before another attempt; pressing again should not create a duplicate charge or message. This recovery behaviour must be implemented and proved before live use.
Agree the connection before setup.
A useful onboarding conversation ends with a clear owner, a narrow scope and a way out. It does not need your whole CRM exported into every service.
Whose account is it?
Name the agency administrator, exact account, number or domain, and who can recover access. Posa sign-in does not grant permission to a provider account.
What may move?
Agree fields, direction and review. Booking approval is separate from a provider accepting a message, and newsletter permission is separate from an enquiry.
What does it cost to leave?
Agree setup and provider charges, export scope, removal of Posa’s access and the handling of retained history. No connection allowance or exit service price is promised here.
Questions before you connect.
Ownership and availability should be clear before an agency hands over access.
Are these integrations working today?
No. “Selected” records a provider choice; “Planned” records the intended connection. Neither means an adapter is live or your account is connected. Use the availability summary to see what can be evaluated now.
Do we have to use a Posa WhatsApp number?
The direction is your agency’s business account and number. The provider route and number setup still need to be proved, including any effect on your existing app or history. Personal WhatsApp sessions are not captured.
Will Posa replace our email and campaign tools?
The initial direction is agency-branded system messages and supported replies, with campaign design and sending in Mailchimp or Kit. Full Gmail or Microsoft mailbox sync is outside the initial connection scope.
Who keeps the accounts if we leave?
The agency-owned model keeps provider accounts, number and domain with your agency. The supported disconnection, Posa data export and retained-history arrangements need to be agreed before a live rollout; this page is not an implemented exit service.
Are provider fees and setup included?
Website services, migration, connection setup and usage allowances still need a defined scope and price. Provider charges may apply separately. Approved Posa plan prices and the distinction between Posa and Stripe fees appear in launch pricing.