Marketing campaign
A product launch, email sequence, ad spend calendar, webinar, and sales one-pager. Success is audience reach, leads, and launch day—not a system going live.
Precision Foundry is not a good fit
Campaigns, events, and office workflows need a different kind of tool
Precision Foundry is not a good fit for that work. It turns a software idea into a reviewable plan. If you are running a marketing campaign, an event, or a standard corporate workflow, use a general team tracker instead.
The projects people often mean
These are real, important projects. They are just a different kind of work than specifying and delivering software.
Event
A conference, gala, or trade show. The work is venues, vendors, booth staff, print deadlines, and day-of runbooks.
Corporate workflow
A policy rollout, quarterly close checklist, onboarding packet, or recurring office process. The work is coordination, dates, and owners.
The line that matters
Precision Foundry can help when you are changing software that supports those operations. It is the wrong shape when you are running the work itself.
Use Precision Foundry
Use a team tracker
Build registration, scheduling, or volunteer software for events.
Run next month’s trade show: booth staff, vendor POs, and print deadlines.
Specify a landing page, CRM automation, or webinar platform change.
Run the campaign: copy calendar, ad spend, and who sends each email.
Replace or improve the expense, intake, or onboarding system.
Update the expense policy and walk people through the current process.
Forced through the workflow
How it would work if you tried it in Foundry
You can create the item. Foundry will still treat it as a software request that has to earn a business case, two estimates, approval, and a gated delivery plan.
- 1
Start a software-shaped project
There is no campaign or event type. You still choose from software categories such as new project, enhancement, or research. A business area like Internal IT or Custom only changes how discovery questions are worded.
- 2
Capture Project Intent and Project Value
Describe the need in everyday language as Intent Items, confirm a Project Brief, and justify why this deserves capacity over other work. Foundry is asking for an investment case, not a due date.
- 3
Pass review, discovery, and two estimates
Intake Review looks for clear Project Intent, owner, metrics, scope, and risks. Discovery asks about systems, reporting, and what must stay unchanged. Then both a business estimate and an IT estimate are required before approval.
- 4
Wait for approval and a priority slot
The campaign sits on the same Priority Board as a payroll integration. You cannot skip ahead to a working task board.
- 5
Plan delivery as epics, stories, and criteria
Approved work becomes requirements, then epics, user stories, acceptance criteria, tasks, delivery teams, and a Technical Design decision. Even Fast Track still requires a story, acceptance expectations, an approved task, a team, and a design decision.
- 6
Execute on a software delivery board
Development Readiness confirms buildable scope before development tracking opens. Testing covers QA, user acceptance, and validation. Release covers readiness, deployment, communication, and production handoff—not event-day runbooks or campaign go-live checklists.
A Q4 launch campaign, translated
If Marketing forced a six-week launch through Foundry, the work would be rewritten as software artifacts so the gates would open.
How a marketing campaign maps onto Precision Foundry artifacts
Requirement
Campaign translation
Prospects can register for the launch webinar from a public landing page.
Epic
Campaign translation
Campaign site, email nurture, and measurement.
User Story
Campaign translation
As a prospect, I can register and receive a confirmation email.
Acceptance Criterion
Campaign translation
Submit shows confirmation and creates a CRM contact tagged Launch-Q4.
Task
Campaign translation
Write copy, design the hero, configure the form, and check the confirmation path.
Technical Design
Campaign translation
Architecture and integrations—or mark Not Required so Development can start.
Testing / Release
Campaign translation
Software QA and production handoff—not “did the webinar run.”
| Foundry artifact | Campaign translation |
|---|---|
| Requirement | Prospects can register for the launch webinar from a public landing page. |
| Epic | Campaign site, email nurture, and measurement. |
| User Story | As a prospect, I can register and receive a confirmation email. |
| Acceptance Criterion | Submit shows confirmation and creates a CRM contact tagged Launch-Q4. |
| Task | Write copy, design the hero, configure the form, and check the confirmation path. |
| Technical Design | Architecture and integrations—or mark Not Required so Development can start. |
| Testing / Release | Software QA and production handoff—not “did the webinar run.” |
Why this feels like over-engineering
- You cannot jump to a board of tasks and due dates.
- Every planning artifact still moves Draft → Needs Review → Reviewed → Approved.
- An IT estimate is a first-class gate, even when the work is mostly copy, vendors, and a calendar.
- Fast Track loosens approvals. It does not remove stories, acceptance expectations, tasks, teams, or a design decision.
- Issues are for defects and incidents, not campaign tasks.
- Testing and Release are software quality and deployment workspaces, not event or campaign runbooks.
What to use instead
When the work is the tasks themselves—owners, dates, checklists, and status—a general team tracker is the right tool. Asana, Leantime, and similar products are built for that.
- Create a project and start assigning work the same day.
- Track copy, vendors, booth staff, and deadlines without writing user stories.
- Move dates and owners without invalidating a delivery plan.
Software change
When Foundry is the right tool
Use Precision Foundry when the organization is deciding whether to change software, and needs shared Project Intent before anyone starts building.
- A new system, or a meaningful change to one that already exists
- Integrations, data, permissions, or reporting that more than one team must agree on
- Business and technical effort that should be estimated before a yes
- A decision record leaders can stand behind, then a plan the delivery team can follow
Common questions
Questions about non-technical projects
Can we manage a marketing campaign in Precision Foundry?+
You can create the item, but Foundry will treat it as a software request. You will still capture Project Intent, justify value, answer discovery questions, complete business and IT estimates, get approval, and plan epics, stories, and acceptance criteria before a working board opens. A campaign calendar belongs in a team tracker.
What about events?+
If the work is software that supports events—registration, scheduling, or operational reports—create it as a software project and pick the closest business area, or Custom. That does not turn Foundry into an event-operations tracker for staffing, vendors, or day-of runbooks.
Is Fast Track meant for non-technical work?+
No. Fast Track is the lightest software-delivery planning profile. It still requires a user story, acceptance expectations, an approved task, a confirmed delivery team, and Technical Design approved or marked Not Required.
What if the campaign includes a real software build?+
Put the software change in Precision Foundry—the landing page, CRM automation, or registration system. Keep the campaign calendar, creative reviews, and launch-day checklist in a team tracker. One tool does not have to hold both.
If the work is a software change, start with the idea.
Precision Foundry is for turning that idea into a plan people can understand, approve, and deliver. Campaign calendars and event runbooks belong elsewhere.