What Ovrture does, what it runs on, and who works in it.
Ovrture asks for time, money and a change in how your office works. A decision that size deserves a clear picture first. The eight sections below are where to start.
- 01Foundations
The record, the sites, what comes back→ - 02Capabilities
Stories in, and what the donor read→ - 03Integration
It runs on the data you already hold→ - 04Content creation
Who will have to write all this→ - 05Organizational complexity
Units, roles and who may change what→ - 06Partnership
Training, support, what is included→ - 07Security and compliance
What your security office will ask for→ - 08Common questions
What comes up in a first demo→
What the platform is, underneath the capabilities.
One record from the system you already keep. The websites that record needs, a stewardship report, a cultivation site, or both. What the donor read, returned to the record. Everything in the sections below is built on those three moves.
The three moves
A picture of the record panel as a development officer sees it: name, assigned funds, giving history, contact preferences, last contact report. The screen a reader recognizes as their own system rather than ours.
- Must prove
- The starting point is data the institution already keeps.
- Must not
- Name a real institution, a real donor, or any CRM's branding.
It starts with the record you already keep.
Every donor website begins as a constituent record in your CRM: name, assigned funds, giving history, the fields your team already maintains. Nothing is retyped to get started.
A layered composition: the Ovrture Institute of Technology site in front, with several of its impact reports fanned behind it. One record, one cultivation site, and the stewardship reports that follow year after year, visible in a single frame.
- Must prove
- Personal at the level of the individual donor, not a template with a name dropped into it.
- Must not
- Use stock photography, or set type over an image.
One record, as many websites as the relationship needs.
One record can carry a stewardship report every year, a cultivation site while a case is being made, or both. Which comes first depends on where the relationship is, and each one is built for one person from data you already hold.
The analytics page beside a session recording: which sections were opened, in what order, and how long each one held attention. The recording is the part that makes it concrete.
- Must prove
- The loop closes on the donor record, not in a separate reporting tool.
- Must not
- Show an engagement rate, an open rate, or an average time figure. All are barred until sourced.
What was read comes back to the platform (and your CRM).
Engagement lands in the platform and returns to your CRM, so communications, stewardship and the development officer who owns the relationship all work from the same picture of what a donor read.
Gathering the stories, the proposal, the report, and what was read.
Four capabilities in sequence. Each one produces something a donor actually opens, and each one leaves behind what the next one needs.
A short, warm request landing with a program director or a scholarship recipient. Two or three questions, a place to attach a photograph.
- Must prove
- Answering is light work for the person being asked.
Stories
Surveys go out from your own email tool, asking the people a gift reached what changed. Their words and photographs come back ready to place in a report.
A list view: eight or ten prospects, each with a site, its status, and when it was last opened. The working screen of someone carrying a portfolio.
- Must prove
- A working tool used weekly, not a one-off production.
Proposals
A private website for one prospect, carrying the ask, the case and the people behind it. You send the link before the meeting rather than a bound document after it.
Not the top of the report: the section further down where the endowment's performance, the awards it made and the students it reached sit together.
- Must prove
- Real fund reporting, not a brochure with a photograph in it.
Reports
The impact report as a website built for that donor, from the fund data your finance office already produces, for everyone in the same cycle.
Which sections were opened, in what order, over which visits. Enough to tell a development officer what to lead with next time.
- Must not
- Show any rate, average or benchmark figure. All barred until sourced.
Engagement
What was opened, what was read and how long it held attention returns to the donor record, where communications, stewardship and the development officer who owns the relationship all see it without asking anyone for a report.
It runs on the data you already keep, whether or not your CRM is connected.
Your CRM is the system of record and stays that way. This is the layer that turns what it already holds into something a donor opens. Most institutions begin by sending a structured file, and that is a complete way to run: the same donor websites, on the same schedule, with nothing missing. A direct connection to Blackbaud CRM or to Salesforce takes the file out of the process when your team is ready. Both are in the license, and which one you start with is your decision rather than a condition of buying.
How it connects
Data flows
- Record data. Name, addressee, salutation, email, and the funds assigned to that constituent.
- Fund data. Fund details, performance, fiscal-year donors, and the impact your finance office reports.
- Your own content. Stories, photographs and copy your team already holds, uploaded or written in the browser.
- Engagement. Opens, sections read and time on page, returned to the constituent record.
- Snapshots. A fixed copy of what a donor was shown, on the date they were shown it.
- Record and fund data. Anything the system holds, back out through the same path it came in.
- A print-ready export. For the donor who wants it on paper.
Managing your data
The screen where a constituent field in the institution's system is matched to its place here. The institution's own field names are legible and they are not renamed.
- Must prove
- The institution's vocabulary survives the connection.
- Must not
- Show a CRM's logo or product name. Connection status is stated on Integrations, never here.
Your field names, kept as your field names.
Mapping is done once, in your institution's vocabulary. Nothing is renamed to suit us, and your team reads the screen without a translation.
The spreadsheet a team without a direct connection actually sends: columns headed and populated, thirty or so rows visible, nothing exotic in it.
- Must prove
- The manual path is ordinary work, not a project.
- Must not
- Show a real constituent, a real staff email address, or a real institution.
Most clients start with an upload.
A structured file does the same job as a direct connection: the same donor websites, on the same schedule, and what a donor opens is identical either way. Connecting your CRM is a step you take when your team is ready.
One system, as many units as you need.
Schools, hospitals, affiliated foundations, and the units inside them. Each publishes under its own mark, to its own donors, with its own people, and central advancement still sees across all of it.
Permission and branding
Roles down the side, actions across the top, ticks in the cells. The screen an IT reviewer wants to photograph and take into a meeting.
- Must prove
- Access is granular and it is administered, not negotiated.
- Must not
- Be so wide it has to be shrunk to fit. Crop to the rows that matter.
Roles are set per unit, by an administrator.
Roles down the side, actions across the top, set per unit. A school's people see the school's work, and central advancement sees across all of it.
One institution's medical center and its college, side by side: different marks, different color, the same underlying report structure. Invented institutions, self-evidently invented.
- Must prove
- A unit is not a folder. It looks like itself.
- Must not
- Use a real institution's identity, even a client's, without written permission.
One system. Each unit still looks like itself.
A medical center and a college publish under their own marks from the same underlying report structure. A donor sees the unit they gave to.
Training and support are unlimited.
An advancement office has to change how it works while it keeps working, and the change lands on people who already have full jobs. Champions move on. New staff arrive in the middle of a year, after the training everyone else got. So the training does not run out, counsel on adoption is part of the engagement, and none of it is metered: a question in year three is answered the same way as one in week three.
A working session, and what the license covers
Two or three advancement staff around one screen with someone from Ovrture, mid-question. Notepads, coffee, a real room or a real video call. Nobody presenting at anybody.
- Must prove
- Support is a person who knows the work, available after launch as well as before it.
- Must not
- Be a stock photograph of a headset, a call center, or a smiling group around a laptop.
Training does not stop at launch.
Training is unlimited and it continues after go-live, so whoever joins your team next is trained the same way the first group was.
A plain list rendered as type: training, support, counsel on adoption, every CRM connection, the open API. Each with the word Included beside it. No pricing, no tiers, no comparison table.
- Must prove
- None of this is a separate line item.
- Must not
- Show a price, a tier, or a competitor. Pricing belongs on Pricing.
Nothing here is a separate line item.
Training, support, counsel on adoption and every connection to your other systems come with the license.
Your reviewer will ask for a list. Most of it is already written.
A SOC 2 Type 2 examined over a full year, a TX-RAMP Level 2 certification, and a trust portal anyone can open. Your security office can run the first pass without us in the room.
What comes up in a first demo.
These come up on nearly every call. They are here so that finding out does not cost you a meeting.
Does Ovrture connect to Blackbaud and Salesforce?
Yes. They are two separate connections. Blackbaud CRM syncs constituent and fund data and returns session-level engagement to the record. Salesforce is available through the AppExchange and logs what a donor opened to the contact record. An institution on any other system connects through the open API. Integrations names every connector and says what each one syncs.
Does Ovrture send the email to the donor?
No. Your own email tool sends the link, from your own domain, so it arrives looking like everything else your institution sends and your deliverability stays yours. The platform has no email sending of its own, by design.
What if a donor forgets the passcode?
A donor site opens with a passcode or with a single-use link sent to the donor's own address, so there is a second way in that does not depend on anyone remembering anything.
How many funds can one report carry?
One report carries many funds, each with its own details, performance and impact, so a donor with a complicated portfolio sees all of it in one place rather than in four attachments.
Can we correct a report after it has gone out?
Yes. You edit and republish, and the donor sees the corrected version at the same link they already have. What was shown before is kept, so your team can always say what a donor saw and when.
Can we still print it?
Yes. Some donors want paper and some boards require it. The platform produces a print-ready export of a donor's report so the printed version is the same document rather than a second one your team builds by hand. Ovrture does not print or mail it: your own print partner does.
Will it look like ours?
Yes. Your identity is built into the panels and the templates during implementation, and a unit's own mark sits inside it. What a donor opens looks like it came from your institution because it did.
Orchestrating the final mile.
Every advancement office runs into the same ceiling. Your hundred best donors get something written for them, everyone else gets a version of the same letter, and nobody chose that; the hours did. All the while your CRM holds more about each of those people than anyone on your team has time to read.
AI co-creation will change that arithmetic. What your record already holds, and the stories your people have already gathered, will become a first draft for each donor, and your team will edit it, decide, and send it. The size of your staff will stop deciding how many donors hear what their giving changed. The judgment those drafts start from comes from Foster Avenue, the campaign counsel practice behind Ovrture.