diff --git a/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/formbricks-sneak.png b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/formbricks-sneak.png
new file mode 100644
index 0000000000..b6b4dcc398
Binary files /dev/null and b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/formbricks-sneak.png differ
diff --git a/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/index.mdx b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/index.mdx
new file mode 100644
index 0000000000..7eb1e9c0fc
--- /dev/null
+++ b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/index.mdx
@@ -0,0 +1,169 @@
+import Image from "next/image";
+import LayoutMdx from "@/components/shared/LayoutMdx";
+import Tellform from "./tellform.png";
+import Tripetto from "./tripetto.png";
+import Ohmyform from "./ohmyform.png";
+import Snoopforms from "./snoopforms-how-it-began.png";
+import FormbricksSneak from "./formbricks-sneak.png";
+import Wrestling from "./wrestling.jpg";
+import TypeformValue from "./typeform-value-prop.png";
+import ResponsiveEmbed from "react-responsive-embed";
+import { Callout } from "@/components/shared/Callout";
+
+export const meta = {
+ title: "Why Qualtrics beats Typeform, especially Open-Source",
+ description:
+ "We kicked it off with a Typeform open-source alternative. As we build and learn, our focus is shifting. Read why:",
+ date: "2023-03-24",
+};
+
+
+
+_In September, we kicked it off with a Typeform open-source alternative. As we build and learn, our focus is shifting. We talk about how we look at form and survey tools today, why experience management not only matters for enterprise and why the endgame looks a lot more like open-source Qualtrics. Qualtrics? What happened to Typeform?_
+
+Let’s dive in 👇
+
+## How it started
+
+
+
+Matti and I kicked off our work on [snoopForms](https://snoopforms.com) as the “Open source Typeform Alternative” - and we weren’t the first to try this:
+
+
+
+
+
+TellForm and OhMyForm were given up, Tripetto niched down to the WordPress ecosystem and are doing quite well selling $99 / year licenses.
+
+The snoopForms launch went pretty well: Within a month, we accumulated 1k+ ⭐ on GitHub, over 1k signups and stirred up quite some interest on [HackerNews](https://news.ycombinator.com/item?id=32303986) and [ProductHunt](https://www.producthunt.com/products/snoopforms). We sold several Early Bird Deals for $179 a piece granting Early Birds 2.500 free monthly submissions for a lifetime. Since the launch in September we have processed several thousand submissions with a ca. 50/50 split between self-hosted instances and our Cloud.
+
+# So what’s the problem?
+
+All of the above looks good. And yet, we decided to move away from a general purpose no-code form builder. To understand why we have to look at three aspects and how they interact: 1) The appeal of open-source ssoftware (OSS), 2) the people we attracted and 3) the value Typeform offers. Let’s lay out the facts first:
+
+1. **The appeal of “open source”**
+
+We wrote about that in more detail in [Open source forms will save the world](https://formbricks.com/blog/open-source-forms-will-save-the-world) but in short, there are three benefits for customers: Data privacy when self-hosting, full customizability & extendability and a weaker lock-in.
+
+2. **The people we attracted**
+
+We attracted two groups of people: No Coders and Coders.
+
+- For most No Coders “open source” means free. About 90% of the people we talked to in our Discord and in interviews find Typeform too expensive for what it does. They don’t care too much about data privacy or code-based customizability and are not really bothered about a lock-in as they usually operate in small organizations (1-10 people).
+- The more interesting group were the hackers and digital agencies taking snoopForms apart and building their own solutions with it. We had an agency building feedback functionality into an e-learning platform run by the State of Geneva (CH) and an online academy in Africa building an assessment center around forms. They loved that they could build their solutions in a fraction of the time, however it still required some custom development to achieve their goal.
+
+The first group isn’t a tempting cohort to build for: They are very price-sensitive and quick to jump ship in a commoditized space. The latter are a better target group but we would run into an incentive dilemma sooner than later: The better the OS offering, the wider the distribution but the harder it gets to monetize. More on why the play book for commercial open source wouldn’t play out well for the Typeform case later on.
+
+3. **The value of Typeform**
+
+Typeform makes forms look pretty and thereby claims to achieve a higher conversion rate than other form tools. Here is the key value proposition from typeform.com (24.03.23):
+
+
+
+The average conversion rate of an emailed out Typeform is 5%. In-app surveys for example average out at [30% so 6x better.](https://news.ycombinator.com/item?id=30377349) Typeforms are the most pretty forms out there and likely to convert better than a Google Form but are by no means the best way to get insights from your audience.
+
+Secondly, according to our user interviews, the people using Typeform aren’t really happy with it. It's too expensive for a form builder and not specialized enough to solve a specific business problem. Rarely do product managers want “more pretty forms” but rather “understand what users think about their product” or “generate leads”. Typeform isn’t specifically built for that. Using Typeform it is still YOUR job to research and implement the best approach for getting the right insights from the right users. This means:
+
+- Coming up with the right set of questions
+- Create the form without leading answers
+- Identifying and reaching the correct user cohort
+- Analyzing and interpreting the data, preparing a report
+- Drawing the correct conclusions from the data to make a better decision
+
+Doing it once requires a lot of skill, knowledge and manual work. Doing it repeatedly and with consistency - especially in larger companies - is really hard.
+
+Typeform makes pretty forms and is kind of stuck doing so because they have to keep serving all kinds of different users building forms for different purposes. One-size fits all fits no one really.
+
+### Why OS Typeform can work as a business (but not at venture scale)
+
+The Commercial Open-Source Software playbook in a nutshell is this: Grow with community and then sell into enterprise bottom up. Let's look at how the Typeform case would do:
+
+**The first part is doable:** Grow a community with a largely free and open-source Typeform clone. We might even make money offering a hosted version for No Coders and people who don't want to self-host. It would be one of many form builders with a capped upside, when Tally.so offers 95% of Typeforms features for free - and then charges $29 / month.
+
+For coders to be able to hack around with the code, it needs to be largely MIT licensed. With AGPL it wouldn't be allowed to build a proprietary solution on top of it and monetize it. MIT is great for distribution but really hard to make money with.
+
+So you have to **monetize with enterprise or government licenses.** But why would an enterprise or government customer pay $$$ for a self-hosting license? They already have a generic form builder - it’s not as pretty, but does the same thing. And by the way, both Typeform and Jotform offer self-hosting for enterprise clients. What’s the differentiator that allows you to drive outsized returns to become the unicorn investors bet on?
+
+It certainly can be a nice lifestyle business to sustain a small team. It’s not a venture scale opportunity.
+
+# Bye Form Creation. Hola Experience Management?
+
+And yet, the yawning gap for an open-source form and survey tool kept us engaged. So we dug deeper. Before we zoom in, let’s zoom out for context:
+
+Broadly speaking, forms fall into two categories: 1) Processing information usually when digitizing a previously analog process. And 2) looking into your customers’ or employees' brains to make better business decisions.
+
+The first category is less interesting to us mostly because no one used snoopForms for it and only a handful of people named it as their objective in user interviews. Also, [anecdotal](https://medium.com/san-francisco-digital-services/how-to-make-a-form-d1d1b67d95d7) [evidence](https://medium.com/@jgee/what-i-learned-in-two-years-of-moving-government-forms-online-1edc4c2aa089) suggests that getting analog institutions to use digital tools doesn’t sound like fun.
+
+The second category is more broadly referred to as “Experience Management” (XM) popularized by Qualtrics. Qualtrics made $1.46B in revenue in 2022 (Typeform will make something between 100M and 120M). Both are impressive numbers **and** a good indicator that generic form creation does not create as much value as helping companies improve customer experiences to grow their business. Both tools are built on “forms”, so what’s the difference exactly?
+
+
+ Qualtrics took the business objective of their customers and productized an opinionated, research-based
+ solution that excels at analyzing large amounts of qualitative data in a way that guides decision-making.
+
+
+Typeform makes pretty forms. It’s no surprise that especially large companies are willing to pay $5000+ / month for Qualtrics while you hear complaints about the $49 / month Typeform charges all too often.
+
+The conclusion is obvious: OS Qualtrics is the real opportunity here.
+
+## Qualtrics for the modern growth stack
+
+Coming up with such a vision is easy. But how do we get there? A wise man once compared a large, successful company with a hole which is both wide and deep:
+
+_So you have two choices about the shape of hole you start with. You can either dig a hole that's broad but shallow, or one that's narrow and deep, like a well. […] Nearly all good startup ideas are of the second type._ - [_Paul Graham_](http://paulgraham.com/startupideas.html)
+
+Experience management covers four areas of experiences: Customer, Employee, Product and Brand. To be able to digg deep, we decided to focus on Product Experiences first as the other three are less relevant when the product sucks.
+
+### Product analytics leave a blind spot
+
+To manage Product you constantly need data on things: What are people doing, and why are they doing it. Quantitative analytics tools like Amplitude or PostHog give a very good insight into what people are doing: You can track every click, watch users move through funnels, etc. But they leave a blind spot: Why are users doing what they do?
+
+To answer this question, product managers should talk to their customers. Everyone knows it, some do it. Especially in larger companies, it gets increasingly difficult. Other things become more important, customers grow more heterogeneous. Organizing who talks to which customers is hard, a lot of work is redundantly done in different teams, many survey or interview requests are untargeted and spammy.
+
+This is where Formbricks comes into play.
+
+## Take what’s good, update what’s old
+
+When we redesigned Formbricks, we came up with a set of characteristics the solution needs to pack:
+
+- Fits into modern product / growth stack: Sits between product analytics, CRM and messaging systems like customer.io
+- Easy to get started but mighty for power users
+- Value increases when the user base grows (revenue expansion)
+- Keep “qualitative data for better product decisions” at heart
+- Packs multiplayer mode from the start
+- Has moments of delight (surprise 🤫)
+- Has virality built in (survey links)
+- Allows simple generic form building (good for OS traction and sales argument to replace Typeform / SurveyMonkey / other form tool with self-hosted alternative)
+
+In a direct comparison to Qualtrics, this is how we position Formbricks:
+
+| The incumbent way | → The OS way |
+| ---------------------------------------- | ------------------------------------------------- |
+| Make self-hosting impossible | → Make self-hosting really easy |
+| Keeping business objective in mind | → Keep, that’s gold |
+| Support managing analog experiences | → Excel at digital experiences first |
+| Limit customizability | → Enable 100% customizability |
+| Large set of extensions and integrations | → Same, working well |
+| Prohibitively expensive | → Give away for small teams use (make devs happy) |
+| Only has value when used in enterprise | → Make useful for SMB as well |
+
+# What have we been building?
+
+We did sit a lot in our office, coding away quietly. During the launch of the previous iteration we learned that a limited product neither serves us nor our early adopters well: It doesn’t really help when the prototype is so inflexible that adjusting it to our customers' needs requires custom coding every single time.
+
+And we learned that the best developer experience is no developer experience. In other words: The less time a dev spends on implementing Formbricks, the better.
+
+So we built that. We built a visual form creator, event tracking, user attribute management and an analysis dashboard built for SaaS products. Users can implement Formbricks via NPM or by copying a snippet into the head of their products HTML. That's it.
+
+With the new Formbricks you can **trigger any micro-survey on any event in your web app.** Very soon you can **filter based on user attributes to survey exactly and only the segment of your user** base which offers signal instead of noise.
+
+You can create events either in your code base or with our No Code Event creator. Yep, even a non-technical person can copy the Formbricks code snippet into the `` tag and use our UI to create events to granularly trigger surveys in the web app. **And they can do so in minutes.**
+
+There is so much you can do with it, here is a sneakpeek:
+
+
+
+What all of this looks like in action we’ll share in a product walkthrough video soon. We are super excited to get the new Formbricks into your hands asap.
+
+### Until then, enjoy your weekend!
+
+export default ({ children }) => {children};
diff --git a/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/ohmyform.png b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/ohmyform.png
new file mode 100644
index 0000000000..0d2c5b04da
Binary files /dev/null and b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/ohmyform.png differ
diff --git a/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/snoopforms-how-it-began.png b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/snoopforms-how-it-began.png
new file mode 100644
index 0000000000..6751aaff6c
Binary files /dev/null and b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/snoopforms-how-it-began.png differ
diff --git a/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/tellform.png b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/tellform.png
new file mode 100644
index 0000000000..1fab5b9d79
Binary files /dev/null and b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/tellform.png differ
diff --git a/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/tripetto.png b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/tripetto.png
new file mode 100644
index 0000000000..f40dc7b667
Binary files /dev/null and b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/tripetto.png differ
diff --git a/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/typeform-value-prop.png b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/typeform-value-prop.png
new file mode 100644
index 0000000000..71cda95303
Binary files /dev/null and b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/typeform-value-prop.png differ
diff --git a/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/wrestling.jpg b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/wrestling.jpg
new file mode 100644
index 0000000000..5c12cbf3e2
Binary files /dev/null and b/apps/formbricks-com/pages/blog/open-source-qualtrics-beats-typeform/wrestling.jpg differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-021222/chart-1.webp b/apps/formbricks-com/pages/blog/weekly-update-021222/chart-1.webp
deleted file mode 100644
index 7424e4f271..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-021222/chart-1.webp and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-021222/chart-2.webp b/apps/formbricks-com/pages/blog/weekly-update-021222/chart-2.webp
deleted file mode 100644
index 4b932675d5..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-021222/chart-2.webp and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-021222/chart-3.webp b/apps/formbricks-com/pages/blog/weekly-update-021222/chart-3.webp
deleted file mode 100644
index d0ec1bbcfb..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-021222/chart-3.webp and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-021222/crowd-dev-1.png b/apps/formbricks-com/pages/blog/weekly-update-021222/crowd-dev-1.png
deleted file mode 100644
index e64e73857b..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-021222/crowd-dev-1.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-021222/index.mdx b/apps/formbricks-com/pages/blog/weekly-update-021222/index.mdx
deleted file mode 100644
index e53897e96c..0000000000
--- a/apps/formbricks-com/pages/blog/weekly-update-021222/index.mdx
+++ /dev/null
@@ -1,166 +0,0 @@
-import Image from "next/image";
-import LayoutMdx from "@/components/shared/LayoutMdx";
-import HeaderImage from "../weekly-update-181122/weeklyupdate.png";
-import { Callout } from "@/components/shared/Callout";
-import NewsletterSignup from "@/components/shared/NewsletterSignup";
-
-import Chart1 from "./chart-1.webp";
-import Chart2 from "./chart-2.webp";
-import Chart3 from "./chart-3.webp";
-import Results1 from "./results-1.webp";
-import Results2 from "./results-2.webp";
-import Crowd from "./crowd-dev-1.png";
-
-export const meta = {
- title: "Weekly Summary - 2nd Dec 2022",
- description:
- "And it is December! This week was dominated by working on the Formbricks HQ, Formbricks Charts and the YC interview. Let’s look at it in detail.",
- date: "2022-12-02",
-};
-
-_And it is December! This week was dominated by working on the Formbricks HQ, Formbricks Charts and the YC interview. Let’s look at it in detail 👇_
-
-
-
-# Highlights
-
-- Formbricks HQ almost ready 🚢
-- Formbricks Charts 📈
-- YC Interview 🍊
-
-Let's dive in!
-
-##
-
-# Product
-
-### Formbricks HQ (launching next week)
-
-We made very good progress with the new Formbricks HQ. We rebuilt the use case of the Swiss government adding native feedback functionality into an existing app - super smooth!
-
-
- The Swiss pulled snoopForms apart to build their feedback feature. A few more early users did that which led
- us to build a modular set of tools: they work independently but are well integrated e.g. by the use of a
- shared data schema.
-
-
-Here is a quick run-through to show how our modular setup plays out:
-
-### Step 1: Build the form with Formbricks React
-
-Within a few minutes we spun up the right form. Look how easy radio buttons can be in React, styled with Tailwind CSS 😍
-
-```tsx
-import { Form, Radio, Submit, sendToHq, Textarea } from "@formbricks/react";
-
-...
-
-```
-
-
-
-### Step 2: Pipe it up with Formbricks HQ
-
-We hooked it up with the Formbricks HQ to store the data. The React Lib sends a data schema along with the submission to assure a complete picture of the data. Read more about schemas in our [docs](/docs/formbricks-hq/schema):
-
-```tsx
-
- );
-}
-```
-
-A lot more information in the [Docs, check them out!](/docs/react-form-library/introduction)
-
-### What's next for Formbricks React?
-
-In the upcoming week we're not planning to add more features to it. We'll first ship a version of the Formbricks HQ to offer an end-to-end solution from form creation to submission handling to analysis 👇
-
-## Formbricks HQ Demo
-
-With the YC interview coming up next week, we decided to build an end-to-end demo. We're not focussing on production readiness for now. Expect to get your fingers on it the week after!
-
-
-
-## Feedback tool for the State of Geneva, Switzerland
-
-We were delighted to find out that a digital agency built a POC for a feedback functionality in an e-learning offer from the state of Geneva, Switzerland.
-
-In the call we learned a lot about why they chose snoopForms (privacy-first), how their developer experience has been (pretty good) and what they need in the future.
-
-They are working on a more comprehensive offer for forms & surveys for the Swiss market built on top of Formbricks!
-
-So exciting for us to see that our product and positioning resonates so well 😊
-
-
-
-##
-
-# Community
-
-Shoutout to octalpixel and [Akshu](https://twitter.com/Akshu_on_github) from the EddieHub community for sharing feedback on the React Library. Highly appreciated 🙏
-
-## Listmonk
-
-We chose [Listmonk](https://listmonk.app/) as our Newsletter tool as it is a promising open-source option. So far the setup has been pretty good!
-
-You can sign up to our "Build in Public" list at the bottom of this article to not miss a single one of them 😉
-
-## YC Interview
-
-We got invited! This is obviously very exciting so we spent some time getting our answers crisp. We're talking some alumns to learn from their experience 🤞
-
-## Have a great weekend!
-
-
-
-export default ({ children }) => {children};
diff --git a/apps/formbricks-com/pages/blog/weekly-update-251122/proof-of-concept.png b/apps/formbricks-com/pages/blog/weekly-update-251122/proof-of-concept.png
deleted file mode 100644
index f1afba11c5..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-251122/proof-of-concept.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-251122/storybook for formbricks survey form builder.png b/apps/formbricks-com/pages/blog/weekly-update-251122/storybook for formbricks survey form builder.png
deleted file mode 100644
index 5a795f352a..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-251122/storybook for formbricks survey form builder.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-251122/weeklyupdate.png b/apps/formbricks-com/pages/blog/weekly-update-251122/weeklyupdate.png
deleted file mode 100644
index ef9f9d4a92..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-251122/weeklyupdate.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-270123/index.mdx b/apps/formbricks-com/pages/blog/weekly-update-270123/index.mdx
deleted file mode 100644
index 5a158df9e9..0000000000
--- a/apps/formbricks-com/pages/blog/weekly-update-270123/index.mdx
+++ /dev/null
@@ -1,68 +0,0 @@
-import Image from "next/image";
-import LayoutMdx from "@/components/shared/LayoutMdx";
-import NewsletterSignup from "@/components/shared/NewsletterSignup";
-import HeaderImage from "../weekly-update-181122/weeklyupdate.png";
-import HeroAnimation from "@/components/shared/HeroAnimation";
-import PmfDummy from "@/components/docs/PmfDummy";
-
-import PMFDashboard from "./pmf-dashboard.png";
-import Waitlist from "./waitlist-cr.png";
-
-export const meta = {
- title: "Weekly Summary - 27th Jan 2023",
- description:
- "Great landing page conversion, PMF survey in beta testing and encouraging insights from interviews 👇",
- date: "2023-01-27",
-};
-
-_January is almost over, time flies! What happened this week? Great landing page conversion, PMF survey in beta testing and encouraging insights from interviews 👇_
-
-
-
-## TLDR
-
-- 14,5% conversion rate on landing page -> waitlist 🤸
-- 90 quality leads collected 👀
-- PMF survey widget in vanilla JS shipped 🚢
-- PMF dashboard incl. filtering shipped 🚢
-- Stumbled over 2 custom-built micro-surveying solution in the wilderness
-
-## Landing page & waitlist work great
-
-Last Friday we shipped our new landing page. Since then we had 1.4k unique visitors on our page of which 203 clicked through to our waitlist form (14.5%). We are quite satisfied with the conversion rate and were able to gather 90 leads incl. email this week.
-
-
-
-Our waitlsit survey is quite extensive and gives us a lot of insight on which of the Best Practices we list on the landing page are demanded most. The waitlist is also cool because:
-
-- **Allows us to pre-segment people we talk to in person**
-- **The information informs decision process on what to build next**
-- **We started using our own product daily which is super insightful**
-
-## Product-Market Fit survey in testing
-
-We’ve built the PMF survey as well as the according dashboard to analyze the results. It’s not yet publicly available as we are still testing edge cases. Similar to the Feedback Box it can be styled, sends partial submissions and can be triggered on click or if a condition is true.
-
-
-
-**Key for running the PMF survey correctly is pre-segmentation** (asking only the right subset of the user base). So far, this requires a bit of custom-coding but the processing by the widget works great!
-
-
-
-We desinged the dashboard specifically for the PMF survey. All other tools only offer a generic dashboard. Some **founders and PMs built custom dashboards in Google Sheets or Excel** to properly understand the data and share the insights with the team.
-
-What's really cool is the interactivtiy. Key to the PMF method by Superhuman is to identify the segment in which the "very disappointed" score is the highest. We make this really easy. **We have also played around with GPT to make this smooth and continuous.** Mattis extensive experience with ML will come in super handy down the line :)
-
-## Ongoing convos with PMs and founders
-
-We keep talking to product managers and founders from our extended network. Additionally, the On Deck directory and Polywork have been a valuable source to find impressively skilled people to talk to. The cool part?
-
-This week we talked to two people who are custom-building a micro-surveying tool to gather feedback from users in-app. In the first case, 3rd-party SaaS wasn’t an option due to compliance issues. In the other, the needs are too specific for one of the general purpose NPS tools out there.
-
-A **self-hostable and freely customizable soultion** would saved both teams **days of developer attention 👀**
-
-### #opensourceFTW
-
-
-
-export default ({ children }) => {children};
diff --git a/apps/formbricks-com/pages/blog/weekly-update-270123/pmf-dashboard.png b/apps/formbricks-com/pages/blog/weekly-update-270123/pmf-dashboard.png
deleted file mode 100644
index e8bc4000f2..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-270123/pmf-dashboard.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-270123/waitlist-cr.png b/apps/formbricks-com/pages/blog/weekly-update-270123/waitlist-cr.png
deleted file mode 100644
index b794660209..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-270123/waitlist-cr.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-301222/customer-detail.png b/apps/formbricks-com/pages/blog/weekly-update-301222/customer-detail.png
deleted file mode 100644
index 907ceab006..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-301222/customer-detail.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-301222/customers-xm.png b/apps/formbricks-com/pages/blog/weekly-update-301222/customers-xm.png
deleted file mode 100644
index 3dd7c56fbf..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-301222/customers-xm.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-301222/feedback-box-1.png b/apps/formbricks-com/pages/blog/weekly-update-301222/feedback-box-1.png
deleted file mode 100644
index a3e14e6d7f..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-301222/feedback-box-1.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-301222/feedback-box-2.png b/apps/formbricks-com/pages/blog/weekly-update-301222/feedback-box-2.png
deleted file mode 100644
index c8fd231455..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-301222/feedback-box-2.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-301222/feedback-box-3.png b/apps/formbricks-com/pages/blog/weekly-update-301222/feedback-box-3.png
deleted file mode 100644
index 274cf55ec3..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-301222/feedback-box-3.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-301222/formbricks-xm.png b/apps/formbricks-com/pages/blog/weekly-update-301222/formbricks-xm.png
deleted file mode 100644
index 642d7c18e2..0000000000
Binary files a/apps/formbricks-com/pages/blog/weekly-update-301222/formbricks-xm.png and /dev/null differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-301222/index.mdx b/apps/formbricks-com/pages/blog/weekly-update-301222/index.mdx
deleted file mode 100644
index 80543cf690..0000000000
--- a/apps/formbricks-com/pages/blog/weekly-update-301222/index.mdx
+++ /dev/null
@@ -1,113 +0,0 @@
-import Image from "next/image";
-import LayoutMdx from "@/components/shared/LayoutMdx";
-import NewsletterSignup from "@/components/shared/NewsletterSignup";
-import HeaderImage from "../weekly-update-181122/weeklyupdate.png";
-import ResponsiveEmbed from "react-responsive-embed";
-
-import CDetail from "./customer-detail.png";
-import CXM from "./customers-xm.png";
-import Box1 from "./feedback-box-1.png";
-import Box2 from "./feedback-box-2.png";
-import Box3 from "./feedback-box-3.png";
-import FXM from "./formbricks-xm.png";
-
-export const meta = {
- title: "Weekly Summary - 30th Dec 2022",
- description:
- "Holidays, illness and iterations: The Feedback Box is ready in plain JS and the MVP for the XM dashboard stands. Let’s have a look!",
- date: "2022-12-30",
-};
-
-_Holidays, illness and iterations: The Feedback Box is ready in plain JS and the MVP for the XM dashboard stands. Let’s have a look!_
-
-
-
-### Highlights
-
-- Feedback Box in Vanilla JS
-- Prototype for Formbricks XM
-- Illness and testing setup
-
-
-
-## Feedback Box in Vanilla JS
-
-We first built the Feedback Box in React (as seen in the video) and then rebuilt it in plain JavaScript. We ran several tests and are currently working on the customizable config for colors, contact person and CTAs before we deploy it.
-
-
-
-## Prototyping Formbricks XM
-
-We forked the Formbricks HQ to facilitate the product changes needed for an opinionated XM solution for SaaS startups. This is the first draft of the dashboard to manage user feedback:
-
-
-
-So far, the meta data you get is:
-
-- Category: Idea, Love, Bug
-- Time of Feedback
-- User incl. Email / uuid
-- Device Info
-- Page
-
-And you can act on it by:
-
-- Sending an email (simple mailto: link)
-- Archive
-
-A key insight from user interviews is that the feedback shared with the founders or product team is **always the starting point of a deeper conversation**. To facilitate that we can build category-specific actions:
-
-- Idea / Love: Issuing an in-app interview prompt to schedule a time for this specific user
-- Bug: Linear and GitHub projects integrations
-- Bug: Integration to open support ticket
-- Love: Prepare testimonial for quick share on Social / Landing Page
-- All: Templates to reply faster
-- All: Segment Integration to enrich user profiles
-
-
-
-The feedback box allows to send along as much meta data as you need. Doing so, it’s possible to build up a customer profile over all micro-survey touchpoints in the SaaS app.
-
-
-
-Over time, the properties in the user profiles can be used to create cohorts for contextualized micro-interactions like 1-on-1 interview prompts, handing out SWAG or Product-Market-Fit surveys.
-
-## Influenza and test setups
-
-Unfortunately we have not been spared from an influenza infection, which slowed us down a bit. We took the time to look at the hypotheses we’re building the experience management solution for SaaS startups on. Here are the critical ones:
-
-- **Problem Risk:** SaaS founders recognize that they don’t know enough about their users
-- **Value Risk:** SaaS founders see the value of a systematic, productized approach for continuous in-app discovery and are willing to pay for it
-- **Feasibility Risk:** Even with a small amount of responses we can create sufficient value to keep founders from churning out of Formbricks after a few months
-- **Solution Fit:** Natively embedded surveys drive higher conversion than “bottom right pop-ups”
-
-### Current status of validation
-
-- **Problem Risk** 🟢 **-** Based on our own experience, 11 interviews with the target group and extensive desk research we can say: The majority of SaaS operators know that they don’t know enough about their users.
-- **Value Risk** 🔴 **-** Even though we have two paying customers it is too early to assess. To build more conviction we’ll setup a landing page with a waitlist survey. We’ll also go into direct sales to find 8 more beta users to pay $49 / month.
-- **Feasibility Risk** 🔴 **-** We’re building the prototype right now. Once implemented we will go through a few iterations before we can assess if Formbricks XM provides value for 200 WAUs and up.
-- **Solution Fit** 🟠 **-** On average, in-app surveys convert 6x higher than standalone surveys. However, we do not know yet how natively embedded (inline) surveys perform in comparison.
-
-To gather sufficient data we’re employing a mix of pretotyping (landing page + waitlist survey), prototyping (with customers) and user interviews.
-
-# Guten Rutsch!
-
-See you in 2023🤸
-
-
-
-export default ({ children }) => {children};