Premium Support is a private channel in Slack or Microsoft Teams with the people who write Portwood, on an annual contract priced by the size of your Salesforce org. It's where you ask anything, where your templates actually get built and worked on with you, and it's the insurance that all of it keeps working through the three Salesforce releases a year. It starts with a 30-minute call, so we scope it properly instead of guessing.
The app is free. Support is having us in it with you.
Premium Support is the difference between figuring it out yourself and having the people who build Portwood do it with you — in your own channel, on your own templates.
priced by org size
Premium Support
Where your documents get built, asked about, and kept working.
Ask anything — your templates, your queries, your org — on a one-business-day target
The room where templates get built — drafts, screenshots and revisions go back and forth in the channel, with the people who wrote the engine
Insurance against Salesforce releases — three a year, and your documents keep rendering through every one
In Slack or Microsoft Teams, whichever your team already lives in
An annual contract, priced by org size — and your templates stay yours either way
What stays free, always: the full Portwood app with every feature and unlimited users, the User Guide, the template marketplace, and a public community Slack for general questions about how Portwood works.
Delivered by us
Template Delivery
Quotedper template
Hand us the documents you need and we build them. Each one is quoted once we've seen the document and the objects behind it — a one-page receipt and a board packet that walks four levels of your schema are not the same job.
Priced per document, so complex schemas get built properly instead of half-built to hit a flat rate
Word, Excel, PowerPoint and HTML — not just the formats the agent writes
Built against a sample record from your org, pulling every field it needs
Delivered rendering correctly — not a draft you finish yourself
Yours forever — it lives in your org and keeps running if you cancel
Quoted with the automation, or without it: flows, buttons, bulk runs and e-signature rollout can be part of the same project — we build those too. If you'd rather they went to a partner, or your own team is taking them in house, that works as well.
Not sure how many you need? That's the first thing we work out on the call.
Delivered by us
Automation Build-Outs
Quotedper project
Flows, bulk generation, e-signature rollouts, integrations — built by us, alongside the templates or on their own. Quoted per project once we've scoped it. If you'd rather use an implementation partner, or your own team is taking it in house, we'll go that way instead.
Record-triggered & scheduled generation flows
Bulk & year-end document runs at scale
E-signature workflows end to end
Quoted per project, or handed to a vetted partner if you prefer
Building automations yourself? The User Guide covers Flow actions and bulk jobs — free, like the app.
Send us the document. Get back a template that works.
You don't need to learn merge syntax, wrestle a query into shape, or find out the hard way how a table behaves when it breaks across a page. Send us the document you already give customers and we build it against a sample record from your org — quoted up front, delivered rendering correctly. Then the channel keeps it that way: the people who wrote the engine, on hand for the layout that shifts, the field that gets renamed, and the Salesforce release that moved something under you.
A year at a time
Your documents don't stand still.
A template isn't "done" the day it renders. Salesforce ships three releases a year, your team adds fields and products, marketing rebrands, and new documents keep coming up. Premium Support is what keeps all of it working — which is why it's a membership, not a one-time build.
Someone to ask
New field, reworded clause, added column, fresh logo. You post it in your channel and the people who wrote the engine look at it — no ticket number, no first-line triage repeating your question back to you. We work one request at a time, in the order they land, so turnaround stays honest.
Kept working through releases
Salesforce changes three times a year. When a release shifts something under your templates, we catch it and fix it — before it shows up on a document a customer sees.
Where the work actually happens
The channel isn't a ticket queue you write into and wait. It's where drafts, screenshots and revisions go back and forth until the document is right — your team and ours in the same thread, in the Slack or Teams you already have open.
Support runs on an annual contract, because that's the span the work actually covers — a rebuild, a migration, and three Salesforce releases. Don't renew and your templates keep running exactly as they are: they live in your Salesforce org, yours forever. Renew, and they keep up with it.
How it works
From first call to shipped — and maintained
1
Book a 30-minute call
Pick a time that works. No deck, no demo you have to sit through — bring the documents you're trying to produce and the org they live in.
2
We scope it on the call
You show us the documents you need and we look at the objects behind them. Complexity is most of the price — a flat receipt and a multi-level packet are different builds — so you leave the call with a quote per template rather than a single rate that fits neither.
3
Your channel opens
Once we're agreed, your private channel is set up — Slack or Microsoft Teams, whichever your team already uses — and your invite lands in your inbox. We're in there from day one with your setup details.
4
Kept working, release after release
Salesforce ships three releases a year. Your templates and queries keep up with them, because the people who write the engine are in the channel watching for it.
Let's start with a conversation
Thirty minutes, no deck and no demo you have to sit through. We work out what you actually need, and you leave knowing what it costs.
1 · Which documents do you need?This is the whole scope conversation. We quote each template once we've seen it and the objects behind it, so you leave with real numbers — no discovery fee, no hourly, no open-ended estimate.On the call
2 · Where do those documents come from today?Word files someone edits by hand, a tool you're moving off, or nothing yet. It tells us what the template has to match and what data it needs to pull — which is the difference between a build that lands first time and one that goes round twice.On the call
3 · Who builds the automations around them?Flows, buttons, bulk runs, e-signature rollouts — the implementation that wraps a finished template. Usually us, in the same project as the templates. Sometimes one of our vetted partners, or your own team taking it in house. We'll tell you honestly which fits.On the call
Book a 30-minute call →Premium Support is priced by the size of your Salesforce org — we'll land you on the right tier on the call, so your first invoice is right the first time. It's an annual contract, and every template stays in your org, yours forever, whether you renew or not. Prefer email? support@portwood.dev.
You're all set — welcome aboard. 🎉
Your private support channel is on its way — named after your company, in Slack or Microsoft Teams, whichever you picked on the call. Three quick steps and you're in:
1
Watch for the invite email. Your Slack Connect or Microsoft Teams invite arrives at the inbox we spoke to, usually within 15 minutes — and peek at spam or promotions if it's shy.
2
Accept the invite to join your private support channel. It's just your team and ours — no public spaces.
3
Say hi. We're already in there with everything from your discovery call. Pick up right where we left off.
Why do I have to book a call? Can't I just sign up?
Because the thing that decides what you pay isn't something a checkout form can ask well. Scope is which documents you need built, and that's a conversation, not a dropdown — we've watched people guess at it and buy the wrong thing, either paying for a tier they didn't need or landing in a channel with no idea what to ask first. Thirty minutes fixes both, and you leave with an actual number rather than "it depends." If you already know exactly what you want, say so when you book and we'll keep it short.
Do you still build templates for customers?
Yes — quoted per template. We used to charge one flat rate and it was the wrong instrument: a single-record receipt and a packet that walks four levels of your schema are genuinely different builds, and a flat price either overcharges the simple one or leaves the complex one half-finished. Now we look at the document and the objects behind it and quote each one. Each is built against a sample record from your org, pulls every field it needs, and is delivered rendering correctly rather than as a draft you finish yourself. The automation around it — flows, buttons, bulk generation, e-signature rollout — can be quoted into the same project, because we build that too; it just isn't assumed, so you're never paying for implementation you didn't ask for. We build in Word, Excel, PowerPoint and HTML, so whatever format the document needs to be, that's the one you get. Bring the documents to the call and we'll scope them with you.
Is there a limit to how much I can ask for?
We don't put a meter on your questions. What we do is work one request at a time, in the order it lands, so every member gets a fair share of the team and turnaround stays honest against our one-business-day target. In the rare case a channel's asks run well beyond normal use, we'll have an honest conversation about the right tier, never a surprise charge.
Once my templates are built, why keep the membership?
Because of everything that happens after "built" — Salesforce ships three releases a year, your fields and processes change, and a document that rendered perfectly in March can quietly break in June. The channel is a direct line to the people who write the engine when that happens, rather than a search through release notes. It's genuinely fine to stop, too: the app is free and keeps upgrading either way, and every template stays in your org and keeps running.
How do the org-size tiers work?
Premium Support is priced by the size of your Salesforce org, in bands — up to 50 users, 51–200, 201–1,000, and 1,000+ — because a five-person nonprofit and a four-thousand-seat enterprise generate very different volumes of question. Independent consultants and freelancers running Portwood on their own have their own entry band, as do agencies and consultancies who build Portwood across multiple client orgs. We quote you on the 30-minute call rather than asking you to guess, so your first invoice is correct the first time. Support runs as an annual contract, and if your org grows into a larger band mid-term we leave you where you are and move you at renewal — we don't re-band you mid-year.
How fast will you respond in my channel?
We aim to answer every message in your private channel within one business day, and in practice it's usually much faster. That's a best-effort target — a channel where the people who build Portwood actually read what you post — not a contractual guarantee, and for most teams it's genuinely enough. If your business needs something firmer than that in writing, bring it up on the call and we'll talk through what it takes.
Do you support Microsoft Teams, or only Slack?
Both — we meet you where your team already works. You tell us Slack or Microsoft Teams on the call, and once we're agreed we spin up your private support channel on that platform and send your invite, usually within about 15 minutes. Everything works the same either way: your dedicated channel, one-business-day answers, and the same team on the other end. If your organization uses neither — a different collaboration tool, or a strict security policy — say so on the call and we'll set up a delivery channel that works for you, part of our Enterprise track.
What about automations, bulk generation, and e-signatures?
We build those too — flows, scheduled bulk runs, signature rollouts, integrations — quoted per project, either alongside the templates or on their own. If you'd rather use an implementation partner, or you already have one working in the org, our vetted partners are excellent and price their own work. Meet them here. Either way, bring it to the call and we'll tell you which route actually fits.
How does billing and cancellation work?
Billing runs on Stripe. After the call we send you a payment link for the tier we agreed on, so your card is charged the right amount from the very first payment — no guessing at a checkout screen and no correcting it later. Template delivery, if you want it, is invoiced separately as a one-time flat price per template rather than folded into the subscription. Cancel the subscription anytime from your Stripe receipt or just ask in your channel. Templates live in your Salesforce org, so everything we've built stays yours forever — the app is free and open source, and that never changes.
Found a bug?
Email it over and we'll take a look — sensitive org details are fine. We'll open your message with a short template so nothing important gets left out. Members: raise it in your channel instead and it lands with the team directly.
