diff --git a/apps/formbricks-com/pages/blog/weekly-update-060123/index.mdx b/apps/formbricks-com/pages/blog/weekly-update-060123/index.mdx
index 165dbbb76c..988af69cf9 100644
--- a/apps/formbricks-com/pages/blog/weekly-update-060123/index.mdx
+++ b/apps/formbricks-com/pages/blog/weekly-update-060123/index.mdx
@@ -14,7 +14,7 @@ export const meta = {
title: "Weekly Summary - 6th Jan 2023",
description:
"Happy new year to all of you (and happy birthday to Johannes 🎂). The Feedback Box turned out to be more tricky to embed with a truly native look & feel. Let’s have a look in detail 👇",
- date: "2023-01-02",
+ date: "2023-01-06",
};
_Happy new year to all of you (and happy birthday to Johannes 🎂). The Feedback Box turned out to be more tricky to embed with a truly native look & feel. Let’s have a look:_
diff --git a/apps/formbricks-com/pages/blog/weekly-update-130123/crowddev-feedback-box.png b/apps/formbricks-com/pages/blog/weekly-update-130123/crowddev-feedback-box.png
new file mode 100644
index 0000000000..8c20dfcaab
Binary files /dev/null and b/apps/formbricks-com/pages/blog/weekly-update-130123/crowddev-feedback-box.png differ
diff --git a/apps/formbricks-com/pages/blog/weekly-update-130123/index.mdx b/apps/formbricks-com/pages/blog/weekly-update-130123/index.mdx
new file mode 100644
index 0000000000..67186e1012
--- /dev/null
+++ b/apps/formbricks-com/pages/blog/weekly-update-130123/index.mdx
@@ -0,0 +1,64 @@
+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 { Callout } from "@/components/shared/Callout";
+
+import CrowdDev from "./crowddev-feedback-box.png";
+
+export const meta = {
+ title: "Weekly Summary - 13th Jan 2023",
+ description:
+ "The year kicked off and with it, we’re picking up momentum again. Our niche of B2B SaaS looks promising, we see first signs of validation. Let’s have a closer look 👇",
+ date: "2023-01-13",
+};
+
+_The year kicked off and with it, we’re picking up momentum again. Our niche of B2B SaaS looks promising, we see first signs of validation. Let’s have a closer look 👇_
+
+
+
+## TLDR
+
+- Feedback Box in production 😍
+- More founder conversations, problem validation progressing
+- Roadmap set for next few weeks
+
+## Feedback Box in production
+
+Yesterday, [crowd.dev](http://crowd.dev) merged our PR and put the first ever Formbricks feedback box live! It's really cool to see it out in the wild 🐅
+
+
+_Go check it out at [crowd.dev](http://crowd.dev) - signing up is a good idea anyways 😉_
+
+We opened a PR in another repo today and have several more conversations going. It’s great working with other open source companies because we can implement the tech ourselves and learn what’s working.
+
+We plan to release a self-serve version of the Box in the coming weeks. Right now our approach remains the “Stripe installation” to keep learning fast.
+
+
+ Infamously, the Collison brothers took the laptops of their fellow YC founders and installed Stripe
+ manually. This allowed them to get it live fast and experience the short-comings of Stripe's developer
+ experience first-hand.
+
+
+## More founder conversations, problem getting sharper
+
+We talked to more founders and learned quite a bit about the current approaches for gathering qualitative user feedback. It is a mostly manual process which is often completely decoupled from the in-app experience.
+
+We’re building more and more conviction that the product we have in mind will add significant value in several stages of building a SaaS product. It’s cool to see that niching down to one target group and their problems allows us to go deep. This wasn’t possible while building general form infrastructure.
+
+What’s remarkable is that pretty much **every** founder we talk to ran the Superhuman PMF survey. The tooling and reliabilty of results differ quite a bit. In all cases, it’s a manual, error-prone and time-consuming process 👀
+
+## Roadmap set for next weeks
+
+Now that we both live in the same city, it’s easier to align. With traction building up and an eye towards raising a pre-seed, we walked backwards from where we would like to be with the product to keep the fundraising process short.
+
+Next up is updating our public communitcation and building the PMF survey with our design partners while dogfooding our product. Stay tuned!
+
+##
+
+# Enjoy your weekends!
+
+
+
+export default ({ children }) => {children};
diff --git a/apps/formbricks-com/pages/blog/why-open-source-no-code-is-the-future-of-enterprise-gov-software/index.mdx b/apps/formbricks-com/pages/blog/why-open-source-no-code-is-the-future-of-enterprise-gov-software/index.mdx
index 696e2c3458..8fda9c9eed 100644
--- a/apps/formbricks-com/pages/blog/why-open-source-no-code-is-the-future-of-enterprise-gov-software/index.mdx
+++ b/apps/formbricks-com/pages/blog/why-open-source-no-code-is-the-future-of-enterprise-gov-software/index.mdx
@@ -65,6 +65,7 @@ Well, maybe because everyone wins with No-Code on the rise. No-Code is compellin
days every other social media manager runs 20 variations of an ad to get data on what actually works best. Enabling
people to no-code their own solutions shortens the feedback loop between decision-makers and consumers.
+
The beauty of No-Code is that every stakeholder gets something out of it, something different:
### Why less-technical people ❤️ No-Code