Question 1

How does Gratona Sponsorships relate to Gratona?

Accepted Answer

Gratona Sponsorships is the sponsorship module within Gratona, the AI-native fundraising CRM for nonprofits. The same relationship depth powers the wider platform and Tali, its AI development teammate.

Question 2

Do I need to run a sponsorship program to use Gratona?

Accepted Answer

No. Gratona Sponsorships is the specialist sponsorship module inside the wider Gratona CRM. Your organization can use the donor, giving, event, mission-trip, multi-entity, communication, task, and reporting capabilities without enabling sponsorship. Grants is in private beta.

Question 3

What sponsorship models do you support?

Accepted Answer

Gratona Sponsorships supports configurable one-to-one, community, pooled, and hybrid program structures. Use the demo to map your exact matching, sharing, transfer, privacy, communication, and reporting rules before confirming fit.

Question 4

Can I import data from my current system?

Accepted Answer

Mapped CSV imports are available for donors, recipients, sponsorships, and payment history. The migration plan depends on your source files and relationships and should define field mapping, validation, duplicate review, recurring-payment ownership, and cutover responsibility.

Question 5

Do donors get their own login?

Accepted Answer

A donor portal is available for configured self-service workflows such as giving history, sponsorship information, profile changes, and supported payment actions. The exact portal capabilities depend on your organization’s configuration, permissions, gateway, and communication workflow.

Question 6

Can I embed sponsorship pages on my website?

Accepted Answer

Gratona Elements supports embeddable donor and sponsorship experiences. Confirm the exact component, styling, authentication, event callbacks, and implementation work required for your website before launch.

Question 7

Do you support mission trips?

Accepted Answer

Gratona includes mission-trip workflows for participants, fundraising, tasks, and budgets. Background checks, signatures, payment paths, and other connected services depend on the selected integrations and written implementation scope.

Question 8

How long does implementation take?

Accepted Answer

Timing depends on source data, recurring payments, integrations, validation ownership, training, and cutover scope. Your implementation plan should identify milestones, responsibilities, acceptance checks, and rollback criteria instead of relying on a universal launch promise.

Question 9

What are the actual costs?

Accepted Answer

Current plan details live on the pricing page so we can keep packaging accurate as we experiment. The model is nonprofit-friendly, usage-based, and not per-seat, so adding staff does not change the subscription cost.

Question 10

Does Gratona integrate with our existing tools?

Accepted Answer

Gratona has a public integration catalog and API surface, but availability and workflow depth vary by connector. Review the exact authentication, data direction, field coverage, error handling, and launch state for every integration your organization needs.

Question 11

How secure is donor data?

Accepted Answer

Security depends on the data path, hosting layer, payment gateway, permissions, and deployment configuration. Request the current security architecture and evidence for transport, storage, backups, secrets, access control, vulnerability management, and the payment workflow in scope.

Question 12

What happens if a payment fails?

Accepted Answer

Failure handling depends on the payment gateway, stored-payment method, retry settings, and communication workflow. Confirm the supported status visibility, retry behavior, donor notice, and staff follow-up path for your configuration.

Questions, answered.

Questions? We've got answers.

Bring us the sponsorship workflow your current tools make hard.