Forge
Forge · Continuous creative production

Set the rules once. Keep creative moving.

Agree on rates, turnaround times and ways of working up front. After that, every request moves through a guided, predictable production workflow, without scoping, quoting or rebuilding the process again for every job.

Why it exists

Built for brands that produce creative every week, not every quarter, from one central team or for every dealer, publication or unit they serve. Live with two client networks across print, digital, video and HTML.

One job, brief to approvedLive
1
Brief
2
In pool
3
Producing
4
QC
5
In review
6
Done
12 banner sizes · due 13:30
09:12
12 banner sizes briefed from one formBrief
09:12
Priced rush tier applied · due 13:30In pool
09:14
Claimed by an operator, no assignmentProducing
12:05
Package verified every size presentReady for review
12:40
1 pin, 1 fix reviewed on the assetRevision
13:20
Approved. Finals ready. Invoice line written.Approved
400+

deliverables through a single client's pipeline

90%+

of that work arrived without anyone typing a brief

0

internal fixes billed to you. Every round is attributed.

2h

fastest turnaround tier, clocked from the moment the brief lands

The problem

Tuesday, 9:10 am. A dealer needs twelve banner sizes by early afternoon.

Nobody planned it. Nobody could have. When the business is alive, creative demand is unpredictable, urgent and constant. The tools most teams are given were built for projects that start and end: a kickoff, a scope, a quote, a timeline. Production at volume doesn't arrive as projects. It arrives as a stream. Here is the same morning, twice.

✕In a project tool
RE: RE: RE: FW: Spring banners (v3) FINAL_final2
47 messages · 6 people · 14 attachments
MK
Marketing
Which one is the latest? I have three PDFs called final.
09:25
ST
Studio
Attaching again, sorry, wrong file earlier.
banners_v3_FINAL(2).zip
10:40
DL
Dealer
Can you resend the 300x250? Also is the price the same as last time?
11:55
PM
Project manager
Looping in legal. Who approved the copy on the leaderboard?
13:10
MK
Marketing
The logo is slightly off on one of them, see my screenshot (circled in red). We needed these an hour ago.
Screenshot 2026-09-22 at 15.46.png
15:48
42 more messages, one of them contains the approval
●In Forge
09:12
Brief submitted. Twelve sizes, one form.
The form knows the product. Price computed from the rate card, rush tier applied, due 13:30 in your timezone. Nothing to negotiate, nothing to forget.
09:14
Picked up from the pool.
A free operator claims it. No dispatcher, no assignment meeting, no "who has this".
12:05
Package uploaded and checked before anyone looks.
Every ordered size present at the right dimensions, the right format, the right name. Forge refuses the upload if one is missing.
12:40
Reviewed on the asset. One pin, one fix.
The reviewer drops a pin on the pixel that is wrong. The operator sees exactly that. No screenshot, no red circle, no "see attached".
13:20
Approved. Finals ready. Invoice line written.
Four hours from brief to approved. The round is logged as a client revision, not an internal fix. Everyone can see who did what and when, forever.

Same brief, same people, same deadline. The difference is what the system does between the moments a human is actually needed. Nothing was negotiated, because it had been agreed long before. Nothing was lost, because it all happened in one place.

Our solution

Forge is a method you can log into.

Assemble spent years learning how to produce fast, at scale, without letting quality slip. The answer was never to rush the people. It was to watch where the hours actually went: the waiting between steps, the approvals nobody owned, the same decisions made again on every job, the hours spent chasing information across systems that never talked to each other. Then to take those out of the work and automate them, one by one. Forge is that method, built into software: it holds the agreements, guides the requests, and keeps the evidence.

Once

Terms agreed up front

Your catalogue, rate card, turnaround tiers and included rounds are set when the relationship starts and stay in force. No job begins with a call about price or timing, because the answer already exists.

Guided

Briefs that can't go wrong

Requests start in a wizard built from your own catalogue. Each answer narrows the next question, irrelevant fields never appear, and a brief can't be sent incomplete. The studio starts from what it needs, not from a follow-up email.

Recorded

One record, not five channels

Prices, deadlines, feedback, revisions, disputes and approvals all live on the deliverable. Nothing sits in inboxes, PDFs or shared drives, so the process can be measured, and what gets measured gets fixed.

And when a request doesn't fit the rate card?

It becomes an estimate, inside Forge. An Assemble producer scopes it, you review the quote and approve it where you asked for it, and the price locks before production starts. The one-off job gets the same record as the thousandth.

From request to deliverable

Six moments. The system carries everything in between.

Speed doesn't come from working faster. It comes from not deciding again what was already decided. Every step below used to be a meeting, a spreadsheet or an email. In Forge it is either automatic, or a single click by the one person who has to make the call.

01
Brief

Ask, properly

A wizard built from your catalogue asks only what this product needs, narrows each question as you answer, and won't send an incomplete brief.

02
Price & deadline

Already agreed

The rates and turnaround tiers you signed up to resolve the price and due date on submit. Off the rate card, it becomes an estimate you approve in Forge.

03
Pool

Pulled, not pushed

Operators claim the next job. Work never waits on a manager to assign it.

04
Produce

Verified on upload

Per-product checks on formats, sizes, packages and naming. Bad files never reach a reviewer.

05
Review

On the asset

Pins, regions, pages, timestamps. Approve or request changes, right there.

06
Deliver

Finals and the bill

Approved work is downloadable and billed from the rate that was locked at the start.

All sites · 38 deliverables in flight
38
In pipeline
9
Due today
6
Waiting on you
2
At risk
Spring banners · 12 sizesMelbourne
Ready for review4h · 1h 05m left
Catalogue page 14Brisbane
In production4h · 2h 12m left
Dealer EDM · OctoberAuckland
Revision requested2nd day
Hero video 15sSydney
In production2h · 18m left
Print ad · quarter pagePerth
Approveddelivered 11:52
Visibility

See what is in flight. Then see why.

Because every request, price, round and decision lives in one record, the pipeline is visible as it happens and measurable after. Where turnaround slips, which products draw the most revisions, which briefs come back for more information: those stop being opinions and become numbers you can act on.

  • Turnaround is a clock, not a promise. Two-hour, four-hour and multi-day tiers, computed with cutoffs, weekends and your timezone. The clock pauses while the client reviews and restarts on every revision.
  • Status is derived, never typed. A project is "in progress" because its deliverables are. Nobody updates a board.
  • Evidence, not anecdotes. Revision causes, turnaround compliance and briefing gaps are recorded per deliverable, for the studio and the client alike. Improvements start from the data, not from whoever complained last.

Twelve weeks of one client's pipeline

Illustrative shape of a real tenant's volume. Bars are deliverables completed per week, the line is the share delivered inside their turnaround tier.

080%1084%2088%3092%4096%50100%W1W3W5W7W9W11
Completed per weekDelivered on time
Review

Say it on the pixel, not in a paragraph.

Feedback dies in inboxes. "The logo looks a bit off" means nothing to the person fixing it against a two-hour clock. In Forge, reviewers point at the thing: a pin on a pixel, a box around a region, a page in a PDF, a second in a video. The operator sees exactly that, threaded, with history.

  • Every format, in the browser. Print PDFs, images, video with timestamped pins, and HTML banners that actually play, with a timeline you can scrub.
  • Guests without seats. Send a proof link to someone who does not have an account. They review, comment and decide. The link expires on its own.
  • Decisions you cannot lose. Approvals and change requests are permanent records on the deliverable, not buried in a thread. The question "who approved this?" has an answer.
Spring banners · 300×250V2
1Brand team12:31

Headline is cropped on the right at this size. Can it wrap?

Fixed in V3, wraps to two lines. · Operator, 12:48
2Brand team12:32

CTA colour should be the campaign teal, not the default.

Revision requested · 12:33
Approved · 13:20
What the review screen does

Pins that stay put

Points and regions are stored relative to the asset, so they land on the same pixel at any zoom, on any screen.

Every format, anchored

Comment on a page of a PDF, a second of a video, or one file inside a delivered package. The note is tied to exactly that.

Banners that actually play

HTML creatives run for real, with play, pause, restart and a timeline you can scrub, and a grid to check every size in a set side by side.

A neutral canvas

The review surface is never tinted with your brand colours, so the colours in the creative read true. Judge the work, not the frame around it.

A conversation with history

Threads, replies from the operator, attachments, mentions and edits that keep their history. Whoever needs to know is notified by email, push or Slack.

Approvals with a safety net

Approved too early? Undo it within the window agreed for your account, with a reason. After that, a change becomes a new, priced adaptation.

Accountability

Every revision has a name. Fairness is a feature.

The oldest fight in creative production is "whose fault was round three?". Forge answers it with data instead of memory, the same way for the studio and the client. And because every round is attributed, you can see where rounds come from: an unclear brief, a late change of mind, a studio miss. That is where better briefs and better processes start.

Per client

Rounds you agreed, tracked

Two, three or four included rounds: whatever you negotiated is set on your account. Forge counts every round against it, and extra rounds are priced in advance and visible before you ask for them.

0

Internal fixes billed to you

If the studio's own quality check bounces a version, or an omission is confirmed, that round is attributed to the studio. It never counts against your rounds and never reaches your invoice.

1

Click to dispute, with a trail

Think a round was not yours? Dispute it. Someone decides, with a written reason, and the decision and every change to it are logged. Nobody edits history.

How a disputed round is settled

You only pay for the rounds you asked for. Here is how that is guaranteed.

Clients asked for this before anything else: a clear, fair way to make sure no one is charged for the studio's mistakes. So it is not a policy on a PDF. It is a flow inside Forge, with the same steps for every job.

  1. 1 · On upload

    Studio fixes are marked as they happen

    When an operator uploads a version to fix something the studio's own QC caught, or a confirmed omission, it is recorded as a studio fix at that moment. It never counts as your round.

  2. 2 · You flag it

    Any reviewer can dispute a round

    If a round was the studio's miss, not your change, flag it from the review screen. Reviewers on a guest link can do it too.

  3. 3 · On hold

    Nobody pays while it is open

    A disputed round counts against no one and reaches no invoice until it is settled.

  4. 4 · Decided

    Settled with a written reason

    An Assemble admin rules it a client revision, a studio omission, or no agreement, and cannot close it without saying why.

  5. 5 · Billed

    The invoice follows the decision

    Billing recalculates from the outcome. Nobody edits an invoice by hand, and every step, including any later correction, stays in the log.

  • A warning before extra rounds cost you. Your supervisors can be notified the moment a job goes past its included rounds, before anything shows up on an invoice.
  • Prices locked per job. A job is billed at the rate in force when it was completed. Changing the rate card later never touches past work.
Not a tracker with plugins

Jira and Asana track work. Forge does the work.

Trackers are built for projects that start, run and end. They give you an empty board and a marketplace, and every intake form, status, SLA field, proofing add-on, rate sheet and guest seat becomes something your team builds and maintains. Continuous production needs the opposite: the agreement, the brief, the feedback and the evidence in one system that already knows how a brand and its studio work together. What changes per client is configuration, not the method.

✕ Generic work tracker● Forge
A brief your dealer can fill without training
✕Build a form per client, per product, then maintain it
●A catalogue-driven wizard per client, edited by an admin, no developer
The price of a request
✕A spreadsheet, or a custom field someone fills in
●Computed from the rate card, the build type and the rush tier
A deadline you can trust
✕A date someone typed
●Computed from tier, cutoff, timezone and publish date
Bad files caught early
✕Nothing, or a plugin
●Per-product checks before the upload is even accepted
Proofing
✕A separate product, a separate login
●Built in, same record, same login, guests by link
To know who caused round three
✕Nobody knows
●Stored per version, disputable, audited
Client access
✕Guest seats and licences, scoped by hand
●Brands, sites and dealers are the data model
Work that isn't on the rate card
✕A quote by email, a PDF, an approval in someone's inbox
●An estimate scoped by an Assemble producer and approved in Forge, price locked before work starts
To know where the process leaks
✕Export to a spreadsheet and guess
●Revisions, turnaround and briefing gaps recorded on every deliverable
A client system that only speaks files
✕Zapier and hope
●An adapter layer with inbox, outbox, retries and dedupe
You need
Built for how you're organised

One team or a whole network. Same system.

Some brands brief their creative from one central team. Others produce it for dozens of dealers, publications, stores or business units, each with its own requests and approvers. Forge runs both ways, and a brand can start with one and grow into the other without changing tools.

One team

Your marketing team briefs, reviews and approves.

A single team works with the studio directly: one set of people requesting, following and approving the work. Locations, markets or products can still be tagged on every request, so reporting shows where the work goes, even when nobody outside the team logs in.

A whole network

Every location gets its own seat. The brand keeps the view from above.

Dealers, publications, stores or internal units each log in to their own space. They request through the same guided brief, follow their own work and approve their own proofs, and never see another location's. Brand admins see the entire network in one dashboard, and can brief on behalf of any location.

Who asks for what, and when

In either mode the brand sees demand by location, product, turnaround and cost, as it arrives.

Named the way you work

Dealers, publications, stores, regions, teams: Forge uses your vocabulary, grouped by the attributes that matter to you.

In production

A brand network across two countries, on one platform.

A brand with dealers across two countries brought its whole network onto Forge. Every dealer now requests, tracks and reviews its own marketing assets in the same place, under the same agreed rates and turnarounds. The brand team no longer collects requests by email and forwards them on: it watches demand arrive, location by location, and sees in its dashboard where the volume, the rush work and the revision rounds come from.

Security

Your unreleased work, locked down.

Unreleased campaigns, pricing, internal plans. What moves through Forge is exactly what your security team is paid to protect. So the platform is built on least access, encryption everywhere and a record of every privileged action, and it went through an independent technical and security audit before it carried client work.

Identity and access

Two-factor authentication is mandatory for administrators and anyone with access to billing, with hashed recovery codes. Repeated failed sign-ins are locked out per account and per address.

Every user has a role, and every request is checked against it and against the organisation it belongs to. Access changes take effect within a minute: a deactivated user is out without waiting for a session to expire.

Data protection

Data is encrypted in transit and at rest, with AES-256 on the storage and database layers. Files are served through short-lived signed links, issued only after an access check.

Each organisation's data is fenced off on every read and write. Test environments never contact real users, and third-party creative files run isolated from the rest of the application.

Accountability

Sign-ins, failed attempts, permission and configuration changes are written to an audit log, with secrets redacted. Approvals and review decisions are permanent records that cannot be deleted.

Production errors are monitored without collecting personal data or request contents.

Every connection is encrypted and authenticated
Browser
HTTPS only, HSTS
Strict content security policy, no inline scripts
Files
Signed, short-lived links
Issued per request, after an access check
Database
TLS, certificate verified
Encrypted at rest, AES-256
Events and webhooks
Signed or secret
Signature or secret checked on every call; closed if not configured
Integrations
Least-scope credentials
Only the access the connection needs, revocable
Infrastructure
LayerWhat it does for ForgeWhereProvider certifications
Application hostingRuns the application and its edge network, with DDoS mitigationAWS us-west-2, United StatesSOC 2 Type 2 · ISO 27001 · PCI DSS · GDPR
DatabaseManaged PostgreSQL, encrypted at restAWS us-west-2, United StatesSOC 2 Type 2 · ISO 27001 · HIPAA
File storageBriefs, proofs and finals, AES-256 at restGlobal object storage networkSOC 2 Type II · ISO 27001 · ISO 27701 · ISO 27018 · PCI DSS
Transactional emailNotifications and sign-in emailAWS us-east-1, United StatesSOC 2 Type II · GDPR
Error monitoringApplication errors, no personal data sentGoogle CloudSOC 2 Type II · ISO 27001 · HIPAA
Team messagingInternal studio notificationsUnited StatesSOC 2 Type II · ISO 27001 · FedRAMP Moderate

Forge runs on AWS infrastructure in the United States, through SOC 2 Type 2 and ISO 27001 certified providers. Certifications belong to each provider. The named list of sub-processors is part of your security review.

For your vendor review
  • Where your data lives. The application and database are hosted on AWS in the United States (us-west-2, Oregon).
  • Who processes it. Six sub-processors, one per layer above. Their names and security documentation are shared in your review, and no other third party receives your data.
  • Your questionnaire, answered. We work through your security and vendor-risk review with your team, control by control.
Independently tested · June 2026

Built in from the core. Then tested by someone else.

The controls listed here are part of how Forge is built, not features added on top. Before Forge carried client work, an independent engineering and security firm tested it across eight areas: security, performance, functionality, database, code quality, file storage, business process and deployment readiness. The work combined dynamic application security testing, static analysis, load testing, manual sessions across every role and direct source review, plus 3,792 functional test cases.

Built into the platform
  • ✓Organisation isolation on every request
  • ✓One authorisation gate for every upload
  • ✓Storage paths set by the server, never the browser
  • ✓Rate-limited sign-in
  • ✓Short-lived signed file links
  • ✓Approved files cannot be overwritten
  • ✓Cryptographic randomness for every token
  • ✓Role checks inside every action
  • ✓Two-factor for privileged roles
  • ✓Audit log with secret redaction
  • ✓Strict content security policy
  • ✓Protection against malicious archives
Integrations

Connects to your stack, on your terms.

Your teams shouldn't have to leave the tools they already use. Forge connects to them with the narrowest access that does the job, over encrypted connections agreed with your IT team before anything goes live.

Read-only

Metrics without touching your systems.

Forge reads project and deliverable records from your platform through a read-only credential scoped to exactly that data. It builds the pipeline metrics, turnaround and volume reporting from them, and never writes anything back.

Two-way

Your team stays in its tool. Production runs in ours.

Your project managers keep working where they work today. When they raise a request, your system sends it to Forge with its parameters and assets; Forge builds the job, the studio produces it, and status, proofs and approved files flow back to the original task.

How we connect
REST and GraphQL APIs
OAuth 2.0 or scoped API tokens
Webhooks
Signed payloads, replay-protected
SFTP
SSH key authentication, encrypted in transit
Batch files
XML, JSON or CSV on a schedule
Chat
Slack notifications and link previews
  • Least access, always. Scope is limited to projects and deliverables. Anything Forge doesn't need, it never asks for.
  • Encrypted end to end. Every connection runs over TLS or SSH, and credentials are stored server-side, never in a browser.
  • Every message accounted for. Inbound and outbound messages are logged and deduplicated, and failures alert a person instead of disappearing.
  • Yours to switch off. Credentials are issued by your team and can be revoked at any time, without touching the rest of Forge.

In production today, a two-way integration brings more than 90% of one client's work into Forge without anyone typing a brief.

Automation and AI agents

Rules where rules work. Agents where judgment is needed.

Most of what slows production down doesn't need AI. It needs rules that never forget, and Forge already runs dozens of them. Where a decision really needs judgment, like reading a messy brief or checking a proof against it, Forge is built to take AI agents, designed around what each client needs and accountable in the same way as everyone else on the platform.

Automated today, with plain rules
  • 01Whether a brief is complete, and which questions even apply, from your own rules
  • 02The price, the build type and the rush premium, or that a human quote is needed
  • 03The deadline, with cutoffs, weekends, timezone and the print publish date
  • 04Whether an upload is acceptable: format, size, package structure, every size present
  • 05How many rounds a job has used against its allowance, and when to warn that it is going over
  • 06Whether an approval is still inside its free undo window
  • 07Whether an order from a connected system is complete, a duplicate, a cancellation or a conflict
  • 08Who needs to know, on which channel, for each of nineteen events
Why Forge is ready for agents
Events

Nineteen typed hooks

An agent would subscribe to them the same way a notification channel does today.

Actions

Same guards as a person

Every state change is already a guarded action, so an agent could never do what a person in that role cannot.

Feedback

Findings land on the asset

A pin, a region, a page, a timestamp. An agent's note would sit next to the human reviewer's, in the same shape.

Accountability

Its own name in the log

Every transition already records who did it. An agent would get its own identity and the same trail as everyone else.

Agents, built to your needs
Custom

Briefs from any document

An agent reads a brief sent as a Word file, a PDF or an email, fills in the wizard fields it can support with evidence, and leaves the rest for the requester to confirm.

Custom

Visual QC before review

Compares each proof with its brief and your brand guidelines: sizes, bleed, mandatory elements, logo use and copy, and pins what it finds on the asset.

Custom

Triage and turnaround risk

Groups and prioritises incoming requests, flags jobs whose runway no longer fits their tier, and drafts the estimate or the revision call for a person to confirm.

How they are built
  • Grounded in your data. Agents retrieve from your own catalogue, briefs, guidelines and approved work (retrieval-augmented generation), so their answers come from your context, not the open internet.
  • The right model for each output. Language models such as Claude or Gemini to read and write, image models such as Nano Banana for visual work, and decision models such as Jev where a fast, typed call with a calibrated confidence score is all that is needed.
  • Better with every decision. Each proposal a person accepts or corrects is recorded, and that feedback is used to evaluate and refine the agent over time.
The agent proposes. The record shows it proposed. A person decides. Forge itself is built this way too: developed with agentic tooling, every claim checked against the running code before it is written down.
Let's talk

Show us a real week of requests.

Bring it as it is. We will walk it through Forge with you, from the agreement to the approved file, and you will see where the hours and the information were going.

Read the story again

Forge is built and operated by Assemble Studio.

Book a walkthrough

Tell us a little about your production. We will come back within one business day to set up a walkthrough on a real week of your requests.

We only use these details to reply to you.