DEV Community

Cover image for Looking for partners for Quevvy
Gentil M.
Gentil M.

Posted on Edited on Originally published at gentil.quevvy.com

Looking for partners for Quevvy

Originally published on my blog: https://gentil.quevvy.com/blog/recherche-sponsors-partenaires-quevvy?lang=en

Why I'm writing today

My name is Gentil M. I am building Quevvy from Kigali, in Rwanda. Quevvy will open soon.

I am writing this article to find a partner. My priority is someone who has the means to support the project, and the knowledge — the network — to connect Quevvy to opportunities. Both at once is what I am looking for first. A partner who mainly provides regular financial support also has a place. In short: either they have the means, or they have both.

This is not a fundraising pitch. I will not inflate the project, or invent figures. If you can help Quevvy last until launch and meet the right people, this article is for you.

Quevvy, in a few words

Quevvy is a SaaS ecosystem designed in Kigali. It brings together the tools to create, publish, and grow digital products, with a carefully crafted experience and modern infrastructure.

In concrete terms, the platform is built around several modules:

  • Quevvy Platform, a website builder
  • Quevvy AI
  • Quevvy Canvas
  • Quevvy Publish
  • Quevvy BaaS

The project was first called SiteX. It became Quevvy when the vision went beyond a simple page-building tool. The thread remains the same: helping people create and publish, then grow what they have launched.

Today, the public site is online: quevvy.com. It presents the project, offers a form for beta testers, and makes it possible to contact the team. The next generation of the platform is being finalized. Quevvy will open to the public soon.

I am also looking for beta testers. On quevvy.com, a sign-up form lets you be among the first to hear when recruitment opens. If the subject interests you as a user, start there. If you are considering a partnership, the rest of this article is for you.

The partner I am looking for

I see two profiles. They have in common a real financial contribution. What changes is what the partner brings around that, and therefore the level of that contribution.

The strategic partner is the priority. They have the means to support Quevvy, and they also have a network: connections, doors that open, concrete opportunities. That can mean clients, investors, events, institutions, programs, or other relays that take the project further than I could on my own. For this profile, the financial share is lighter, because the network already covers part of the way.

The financial partner primarily provides regular financial support, at a higher level. They are not necessarily in a position to open doors, and that is not a problem. Their contribution makes it possible to cover costs, prepare the launch, and give Quevvy room to grow.

In both cases, the monthly contribution is defined together. It is adjusted according to what each partner brings: a network and opportunities reduce the financial share. The amounts evolve according to our needs and the stage of the project. Nothing is fixed once and for all. We talk it through, we write down what has been agreed, and we revisit the framework if the project or the collaboration changes.

In-kind cloud and AI credits remain welcome, as a complement: Cloudflare, AWS, Azure, OpenRouter, or another provider of the same kind. A usage credit does not replace the partnership described above, but it lightens part of the costs, especially on the AI side. If you run a startup program, or if you think Quevvy has a place in one, write to me as well.

What this support will be used for

I want the use to be clear, with no detours.

Monthly costs. Hosting and infrastructure, but also the tools and services that have to be paid for every month to keep Quevvy running. This is the foundation. Without it, the upcoming launch does not mean much.

AI tokens and credits. Quevvy AI, and more broadly the parts of the product that rely on language models, consume tokens. The more they are used, the more that costs. Some of these tokens will also be given to new users, to help them discover the product and adopt it. AI usage remains the line item that can rise the fastest; it is also a lever for making the platform known.

Participation in events. Being present, contributing, making Quevvy known, and growing the brand beyond the website. A launch is also prepared off-screen.

The upcoming launch. The weeks before opening, and then the first weeks after, are when I do not want to have to slow the product, or adoption, because costs or AI become too heavy. The support is there to get through this stage properly, not to tell a story larger than the project.

I am not putting forward a global amount, or a detailed usage forecast: too much depends on how people will actually use the platform once it is open. What I can say honestly is what the money and the credits will be used for.

What I can offer in return

A Quevvy partner is not a name forgotten on a list. Here is what I can put on the table, concretely.

Visibility: the partner's logo on quevvy.com, and also at events or around the launch, depending on what we organize. Placement is agreed together: I will confirm it before putting it online or displaying it.

Priority beta access, to use the product early, test it, and tell me what is off.

Tokens possibly offered to new users in the partner's name. If we go in that direction, the adoption gesture also carries your name, not only mine.

Close follow-up, and regular product updates. I prefer a living collaboration: we talk, we adjust, we see what works.

For a deeper collaboration, a more committed partnership or a sharing of interests, we discuss it case by case. I am not promising equity here, or an automatic share of revenue. If a topic of that kind makes sense for both sides, we set it out clearly, in writing, at the right time.

If your profile does not fit exactly into the two categories above, write to me anyway. We can agree on something else, including one-off support rather than monthly support, as long as the framework stays clear for everyone.

How to reach me

The simplest is to write to me at info@quevvy.com. You can also book a call on cal.com/gentil-m/quevvy.

The project site remains quevvy.com. The form for beta testers is on the same page, in the Beta section.

If you are looking instead for development work — a website, an integration, a tool — I have offers on my marketplace. That is not the subject of this article, but the link is there if you need it.

Thank you for reading this far. Quevvy is being built in Kigali, one step at a time. If you can be that partner, or help me find one, I am available to talk.

Top comments (0)