~ 7 min

An investment expert had 900+ newsletter subscribers and 18,000+ site visitors a year, but no way to earn from them. We built the technical side of a paid subscription platform: Stripe payments, a member area with articles and subscription status, automatic granting and removal of access, emails about expiring access and a simple admin for publishing new articles. Everything runs without the author’s manual involvement. In the first 2 months after launch the project brought the author $3,800.

A joint project, 2024. We were responsible for the whole technical side: the database, access logic, payments and subscriptions, automations, integrations and CRM. UX/UI design and layout of all Tilda pages were done by designer David from Migas Studio. The client and the designer approved publishing this case.

Hidden Value Gems is a weekly newsletter with financial ideas from investment expert Ildar Davletshin. He looks for undervalued companies by five criteria: low debt, management ownership, attractive valuation, business quality and strong financials.

By launch the newsletter had 900+ subscribers and the site had been visited by more than 18,000 people in a year. The audience already existed, so the team decided to monetize the traffic: build a platform where the most valuable articles are available by subscription only. Speed mattered, so the deadline was strict: 18 working days.

Problem: there is an audience, but no revenue

- Content is given away for free. Every article goes into the newsletter, so there is no reason to pay.
- Paid content leaks easily. If you just put articles on a hidden page, the link can be forwarded to anyone.
- A subscription is not just a “Pay” button. It can be active, canceled but still paid, expired or lifetime. Tracked by hand, someone gets access for free and someone loses access they paid for.
- Publishing must not become a programmer’s job. The author writes every week and should add an article to the platform on their own, without a developer.

Task

- Run a technical study: how to protect paid content from leaking and how the author can add new articles conveniently.
- Connect Stripe payments: a subscription with auto-renewal, cancellation and resumption.
- Build a member area: articles, profile, subscription status, plan change, cancel and renew, payment history.
- Open and close access automatically by subscription status and warn subscribers before access ends.
- Build a database of subscribers, articles and purchases, that is, the project CRM.
- Implement everything on the designer’s ready design and layout and finish within 18 working days.

Solution: a no-code platform where the subscription runs itself

Designer David from Migas Studio created the UX/UI and built the pages on Tilda, and we “connected the engine to them”. All data about subscribers, articles and payments lives in one database. Every payment event automatically changes the subscription status, opens or closes articles and updates the subscriber’s card. The subscriber manages the subscription in the member area, and the author only has to write.

Example: the journey of subscriber John (illustrative scenario)

1. John, a private investor, has long read the free newsletter and sees a block about the subscription with plans and reviews on the site.
2. He chooses Premium for a month and pays through Stripe. Right after payment the paid articles open in his member area, and a green Active status lights up in the header.
3. Every week a new article appears in the area. The author just added it to the database, and it automatically reached subscribers.
4. In Payment Settings John sees his plan, the next payment date and payment history.
5. A few months later he clicks Cancel subscription. The service asks whether he really wants to cancel auto-renewal and offers Stay subscribed.
6. John cancels. Access stays until the end of the paid period, and a reminder email arrives before it ends.
7. When the period ends, the status changes to No active and the paid articles close. He can return in one click via Renew subscription or by choosing another plan, such as an annual one.

How it works

Content protection and an admin for articles

We started with a technical study: how to keep paid articles from leaking and how the author can publish without a developer. Articles are stored in an Airtable base and shown in the member area dynamically, only to signed-in subscribers with an active status. There is no separate link that can be forwarded. The database itself became the admin: the author adds an article and it appears for subscribers.

Database: subscribers, articles, purchases

We designed and set up the base structure in Airtable. It stores subscribers, articles, purchases and subscriptions, and is in effect the project CRM: the author sees who pays, on which plan and when each person’s access ends.

Plans and every subscription state

The Premium subscription renews automatically. After launch we added a third plan, Lifetime Member: it is paid once and access becomes permanent. Each state has its own data and buttons in the member area:
- Active, auto-renewal on: the next payment date, Cancel subscription and Change plan buttons.
- Active, auto-renewal canceled: an Until date showing when access ends and a Renew subscription button.
- Expired: an Expired since date, buttons to renew or choose a plan, and a link to Premium benefits.
- Lifetime access (added with Lifetime): a “∞” term and a link to benefits.

Cancel and renew go through a confirmation window, so a subscriber will not click by accident and the service gets one last chance to keep them. The Billing history table shows the date, plan, status and amount of every payment, so “was I charged?” questions never reach the author.

Access logic and expiry emails

Make holds the business logic: a payment, renewal, cancellation or end of period in Stripe immediately changes the subscription status in the database, and with it access to articles opens or closes. Through Mailchimp subscribers automatically receive emails about expiring access so they can renew in time. There are no manual “who to unlock” lists.

Live data in the member area

So that the Tilda pages could show personal data (articles, profile, subscription status), we connected 8 integrations through Collabza. They pass data from Airtable straight into the area, and each subscriber sees only their own.

What the designer did

David from Migas Studio did the UX/UI design: references, User Flow, a prototype and an interactive Figma mockup. He also built 11 Tilda pages adapted to all screens, with 15+ modifications and 3,000+ lines of styling code, and refined two site pages with blocks about the subscription, plans and reviews.

Testing and handover

We ran every data-entry form more than 50 times, checked how dynamic content from the database appears in the member area, and gave the project team documentation: instructions and screencasts on working with the platform.

Stack

Tilda — site and member-area pages (layout by David, Migas Studio).

Airtable — the database of subscribers, articles, purchases and subscriptions, also the CRM and the admin for articles.

Make — business logic: payments, statuses, granting and removing access.

Collabza — passing personal data from Airtable into the member area.

Stripe — international payments, recurring charges, cancellation and resumption of auto-renewal.

Mailchimp — the newsletter and automatic emails about expiring access.

Reliability

- Card data never passes through the site: payment happens on the Stripe side.
- Articles are shown only to signed-in subscribers with an active status, with no public links.
- Access changes on payment events, not by hand, so statuses in the member area, the database and access always match.
- Cancel and renew require confirmation.
- All forms were tested 50+ times before launch.

Platform tour

Let us walk through the platform through a subscriber’s eyes, from choosing a plan to managing the subscription. Below are the member-area pages in the Tilda editor and the subscription screen mockups.

1. Choosing a plan

The site has a subscription block with plans and reviews. A subscriber picks a plan and pays through Stripe.

2. Signing in

After payment the subscriber signs in to the member area. The platform takes their status from the database and decides which articles to show.

3. Articles

The main section of the area. A new article appears here every week: the author added it to the database and it instantly opened for everyone with an active subscription.

4. Profile

The subscriber’s data is pulled from the database, and everyone sees only their own.

5. Managing the subscription

The Payment Settings section shows the plan, the next payment date and payment history.

6. Cancellation

Before canceling auto-renewal the service asks for confirmation and offers to stay.

7. The subscription ended

The area shows the end date, paid articles close, and the subscriber can return in one click.

All states in the mockup

Here are all variants of the section, including the lifetime plan that was added after launch.

Project results

- $3,800 earned by the project in the first 2 months after launch.
- 18 working days from start to launch.
- 900+ newsletter subscribers and 18,000+ site visitors a year at the start.
- 3 plans (Lifetime was added after launch) and 4 subscription states in the member area.
- 8 integrations for live data in the area.
- 50+ form test runs.
- 0 manual access operations.

Want to monetize your audience with a subscription?

If you have a newsletter, a blog or gated content and want to sell it by subscription without manually granting access, tell us about the project in the brief. We will work out how to protect the content, which plans and subscription states you need, and build the platform around your payment model.

The 2024 platform runs on Make and Airtable. Today, for such projects we more often use n8n and SeaTable on your own server. We describe that kind of migration in the case “Moving from Make and Airtable to n8n and SeaTable”.

Tech Stack

Tilda logo

Tilda

Airtable logo

Airtable

Make logo

Make

Collabza logo

Collabza

Stripe logo

Stripe

Mailchimp

Results Achieved

18 working days

Delivery Time

$3,800

Revenue in the First 2 Months

0

Manual Access Operations

900+

Subscribers at Launch

Like this case? Launch yours just as fast

Same approach, same speed, same quality. Fill out the brief or calculate your project cost right now.