Inception: using jestor at jestor

Skin in the game is for good and bad times.

We are our first user. We are the most excited user when there's something new and we hurt together with our clients if something is not working as it should. Since day 1, jestor is our main tool to build jestor, and it's just getting better everyday 💪

Our jestor has lots of tables, dashboards and is connected with different apps to automate our operations. We'll show you some examples of how we do it internally.

It's all connected

We only have one jestor with all our different functions in one single place. It's only possible because we connected all our tables and data in a way that grants us data reliability, flexibility to change and grow, great analytics, and automations.

Next, we'll explain how we built our own jestor for each use case 😊

Product Development 👩‍💻

Tools: jestor + GitHub + Slack

  • New features: Our team and clients can suggest new features, which are then managed on a table inside jestor where we evaluate how, what, if and when we will develop it.

jestor <-> jestor

  • Product development: We have a table called "development process" connected to the "new features" table.
    • When a record (or a card in our kanban) on the "New features" table is checked on the field "Needs development?", a new card is automatically created on the development table and a new branch on GitHub as well.
    • The new card is connected to the record that originated it, so all the developers have context of the new feature. Once the code of the product is ready at GitHub, it's automatically linked with the development table (and record), so everybody can review it and test.
    • Finally, when the new feature goes to production (record gets to the phase "Production"), a Slack message lets the entire team know that there is something new in jestor 🎉

jestor -> jestor -> GitHub <-> jestor -> Slack

Website 🖥

Tools: jestor + WordPress

  • Leads: Our website sends and receives data from jestor. Anytime someone creates a new account, our jestor receives the lead.

WordPress -> jestor

  • Templates: All the templates that we have on our website were launched by creating new rows inside our own table with all the information needed for the template page.
    • For example: template link, category, text and image are all information that jestor sends to WordPress so a new page is automatically created.

jestor -> WordPress

Bugs 🐞

Tools: jestor + Slack + Intercom

  • Users' report: we receive bugs through the Intercom chat, which is integrated to our website and our product. All this bug data is sent to jestor by our support team with time rules to reply our users and keep them updated on the matter.

Intercom -> jestor

  • Bugs discussions: all bugs reported are automatically sent to a Slack channel. If it's necessary to go deeper into the problem, we all discuss it and try to get to the solution as fast as possible.

jestor -> Slack

  • Bugs management: we have a group of tables connected (account information, bugs, support and others) with all the information about the bug, prioritizations rules (automations) and development status. A simple and interesting field is the picture field: it helps a lot to understand what happened in each specific case.

jestor <-> jestor

Growth 📈

Tools: jestor + Intercom + WordPress + Mailchimp

  • User engagement: We use our dashboards to analyze in real time if we are building something that our users love or if they just don't care about a specific feature.

  • SEO and Content Management: Our jestor manages all the pipeline of content and social media interactions to help us to produce relevant and helpful content to our users and prospects. Once the text is written, it goes to WordPress, creating a new blog page automatically.

  • Onboarding: Intercom and Mailchimp emails have conditional automations according to the user maturity using jestor. All triggers and metrics are managed by our jestor.

  • Social Media: We track all the costs with social media experiments to understand indicators like CPL, CAC and LTV.

Infrastructure Management 🏗

Tools: jestor + AWS + New Relic + Slack

  • Scaling and Servers: Our jestor monitors, receives and send data to AWS in order to guarantee the maximum reliability of our services with prediction algorithms that run inside our jestor.

jestor <-> AWS

  • Alerts: If jestor is down even for a millisecond, we all are notified by a Slack channel connected to New Relic and our jestor, so we can analyze and act as fast as possible if it's needed.

jestor <-> New Relic <-> Slack

Tasks ✅

Tools: jestor + Slack

  • Tasks to anyone: You know when you're having a discussion on Slack but you're actually giving or receiving to-do's?

    • We've developed a process to send tasks through Slack to jestor, just typing a Slack command and the task. The task is automatically assigned to the person responsible. You can also go to the table at jestor and add tasks manually and it'll send and automatic message to Slack.
  • Manage your to-do's: Some of us have personal dashboards summarizing all the open tasks and number of completed activities with different filters and visualizations to help each of us to track and advance on our daily activities.

jestor <-> Slack

Finance 💳

Tools: jestor + Stripe

  • New paying users: Every time a new paying user is added to an account, our jestor records this data and triggers Stripe to add a new user to that client subscription. Once a client pays for jestor, we receive the information in our tables that are connected with revenue and other business metrics.

jestor <-> Stripe

  • Accounting: We do all our accounting inside jestor in collaboration with our accountants, so any data that they may need is easily extracted using reports.

jestor <-> jestor

  • Startup metrics: We have dashboards tracking all our progress with all famous startup metrics like: net dollar retention, MRR, churn, cohort analysis and others. They are all automatically updated with our financials and product data.

jestor <-> jestor

Venture Capital 💰

Tools: jestor

  • Investment management: we have some tables with all venture firms that we've talked (all the contact info, websites and other relevant data), so we can measure and keep track of all interactions with investors.
    • We use the kanban view to manage all the different stages of our relationship with investors, including firms and people that we want to have a relationship with in the future.

jestor <-> jestor

  • Metrics reporting: all the data that we share with our investors about jestor's growth like MRR, burn rate and others are organized inside jestor. So, the reporting of this data is effortless.

jestor <-> jestor

And more

We are constantly changing all our processes and iterating them so we can always grow faster with a better product to all of our users. Thus, there are many other tables in jestor to experiment with new things and also some supporting tables to make our jestor extremely scalable 🔮

What’s Next