Maya Ellis
Portfolio · selected work
Your agency’s look. A clearer route to a brief.
The agency website plan for Posa’s model and talent agency software brings boards, approved portfolios and client enquiries into one considered journey. Your brand leads; the agency decides what clients may see.
From board to profile to enquiryIllustrative website composition · not a live portfolio
DEVA MODELSExample agency identity
An agency-defined board
Two illustrative profilesNew faces.
Nia James
Portfolio · selected work
Availability subject to agency confirmation.
Maya Ellis
Approved biography, selected media and the public details the agency chooses.
- Studio portraitProposed for public review
- Private casting videoExcluded from the website
A brief with context.
- Client project
- Juniper studio campaign
- Interested in
- Maya and Nia
- Shoot date
- To confirm
Next: a booker reviews the brief. No booking is confirmed.
A website plan, with publication still ahead.
The current tenant site is an unpublished shell. Branded boards, public profiles, connected media and live enquiry intake still need a reviewed publishing service. The composition above is a design example, not an available agency website.
Available now
The standalone free comp-card maker can create a card in your browser. Cards generated from Posa profiles are planned.
Private preview
The staff workspace saves linked agency drafts. A saved talent draft does not make that person or their photographs public.
Before a launch
Agree website scope, media permission, domain ownership, support, costs and a reviewed publication process. No template catalogue, delivery date or hosting allowance is promised here.
A portfolio clients can find their way through.
The design starts with a simple client task: find the right people, understand their work and send the agency a useful brief.
Organise the roster your way.
Agree the agency’s board names, order and public membership. The same talent may need different presentation for different audiences; private or archived records must stay out.
Show the details that matter.
Choose the public name, biography, measurements and approved location details for each profile. Keep missing information honest and private contact details away from public pages.
Curate the work, not every file.
Review images, video, credits, permission and order before publishing. Private originals, casting submissions and contracts are not automatically portfolio content.
Bring the interest into a brief.
The planned handover carries the client’s chosen public profiles and project details to a booker. “Dates to confirm” and “Please advise” stay valid answers, rather than invented dates or budgets.
One deliberate step between private work and public pages.
Being on the agency’s books is different from appearing on the agency’s website. The intended publication process makes that choice explicit.
Website reviewIllustrative checklist
Maya’s public profile
- Include after approval
- Public biography, agreed board, selected images and permitted display details.
- Keep private
- Direct contact details, internal notes, private originals, booking finances and precise private schedules.
- Review again when
- Media permission changes, a profile leaves the board or the agency withdraws publication.
- Choose the public version.
Review the profile fields and exact media clients will see, with the agency’s approval recorded.
- Check the page in context.
Review boards, profile order, mobile layout, enquiry destination and the agency’s branding before launch.
- Keep changes and removals owned.
Agree who publishes updates and checks removal from the website and its caches. Copies elsewhere cannot be promised to disappear instantly.
What if a photo’s permission changes after publication?
The intended service needs a way to withdraw the affected public image, update the profile and clear the copies it controls. It must not restore a withdrawn photo from an old cached page. Removal timing, checks and escalation still need to be agreed and proved before an agency relies on publication.
An enquiry is the start of the conversation.
The fictional Juniper client has browsed Maya and Nia’s profiles. They like the direction, but the shoot date and usage still need discussion.
“We’re planning a studio campaign.”
The proposed brief asks for project, selected talent, contact, dates, location, budget and usage, while allowing genuinely unknown details.
Sending that brief must have a real receipt and a way to recover if delivery is unclear. This page does not collect or submit it.
Fit, availability, fees and rights.
The design brings the enquiry into agency work with its source and chosen profiles. A client’s interest does not reserve talent, grant usage rights or confirm a booking.
Any marketing sign-up would need its own separate choice; it must not be inferred from a project enquiry.
Keep your brand and domain at the centre.
Presentation and operating responsibilities belong in the website scope, before an agency agrees to move its public presence.
Your visual identity
Agree logo, colours, typography, board structure, profile layout and image treatment. Review the real content on compact screens, rather than shrinking the desktop page.
Your existing website
The plan covers a Posa-built branded website or a narrower connection to an existing site. Supported placement, profile routes, enquiry handover and any redirects need a site-specific review.
Your ownership and exit
The domain remains the agency’s asset. Name its administrator and agree hosting, renewal responsibility, content export and disconnection. Website design, setup and hosting charges are not settled.
Questions before a website project.
Agree the real service around the design, including what happens when content changes or the agency leaves.
Can clients browse a live Posa agency portfolio today?
No. The tenant site is an unpublished shell, and this page is an illustration. Boards, approved public profiles and enquiry intake remain publishing work to complete before an agency launch.
Can we keep our existing website?
That is part of the intended direction: a connected roster or enquiry route alongside an existing site, as well as a complete Posa-built website. Compatibility, page ownership and supported placement need review for the actual site. There is no installable universal connector or WordPress plugin supplied today.
Does every saved talent profile become public?
No. Saving a private agency draft is separate from choosing public fields, reviewing media permission and approving publication. Private contact details, internal notes, casting material and financial information must stay outside the public website.
Does a website enquiry hold or book the talent?
No. The intended handover creates an enquiry for agency review. The booker still needs to check dates, options, fees and usage before a booking can be agreed.
Who owns our domain, and what happens if we leave?
The agency-owned direction keeps the domain and brand with the agency. Website scope must name the domain administrator, renewal and hosting responsibilities, export arrangements and how Posa access ends. A complete website handover service is not implemented or priced here.
Are comp cards part of the profile plan?
Profile-generated comp cards are planned. The standalone free comp-card maker works now in your browser, using the photos and details you choose. It does not publish a Posa profile.