Show the work, explain your part A useful portfolio answers what you built, what you contributed and how it turned out.
Choose a few strong projects. Use screenshots or a preview that show the finished work, not just a logo. Name your role and the tools you used. Credit collaborators and distinguish your contribution from the team's. Write a short problem → approach → result story. Only claim metrics and ownership you can support. Build your portfolio Turn an idea into a clear brief The right person can estimate work when the outcome, limits and acceptance criteria are clear.
Describe the feature or deliverable, its audience and what already exists. Include useful references and what is out of scope. State a realistic budget and deadline. Explain the required files, usage rights and how you will assess the result. Ask for relevant work and a short approach. Agree on milestones and revision limits before starting. Write a job brief Package a service people understand A good package defines an outcome rather than promising unlimited work.
Give each package a clear deliverable, delivery time and revision count. State what the buyer must provide. Explain dependencies and exclusions. A larger game system needs a different scope from a single interface screen. Keep agreements and delivery in the contract. If the brief changes, agree on the next step before doing extra work. Create a service Build a team with clear expectations Shared ambition works better when responsibilities and compensation are written down.
Describe the project stage, the next milestone and the people already involved. Open roles should have concrete responsibilities. Label compensation honestly: paid, unpaid or revenue share. Future earnings are uncertain and revenue share is not guaranteed pay. Agree on credit, ownership, communication and how someone can leave. Never ask a teammate for passwords or session cookies. Explore teams and projects Make delivery easy to review A handover should let the client check the agreed outcome without guessing.
Use the agreed milestones and acceptance criteria. Keep an explanation of changes alongside the delivered files. Provide setup notes and distinguish editable source files from previews. Share files through the authorised contract flow. Keep payments and disputes on the platform. A contract is funded only after payment confirmation; a message saying paid is not confirmation. Open your contracts Protect your account and your work A professional collaboration does not need access to your Roblox account.
Never share Roblox passwords, .ROBLOSECURITY cookies, session tokens or recovery codes. Use official account linking and enable two-factor authentication. Avoid off-platform payment requests and unexpected links. Do not buy or sell accounts, Robux or on-platform items here. Use reporting for suspicious behaviour. Review licence terms before using an asset, and credit people for work they actually made. Review account security