
A rebrand to match the product's promise
A new identity delivered in two weeks
61
pages in the brand book for every future asset

10 min read
4WK
The same Figma was stalled with other developers
0
Lighter mobile animations ensured smooth loading, even with power saving on
45
The team now updates website content on their own
If you’ve spent any time around the startup ecosystem, you’ve probably come across accelerators, incubators and institutional VCs. Venture studios are a newer name on that list, and they work quite differently.
In simple terms, a venture studio is an organization built to repeatedly create startups using a shared platform. It helps build the company while getting its hands dirty.
According to StartupFundraising, 84% of studio startups go on to raise a seed round, and 72% of those make it to Series A, compared to only 42% of traditional startups.
On top of it, traditional startups typically take around 56 months to go from Pre-seed to Series A, while venture studio startups need ~25.2 months on average. That’s half the time!
This is exactly why more founders are turning to venture studios. Kartawya Ventures is one of them. But it brings its own twist to the model and works a little differently from what you'd expect.
It gets inside the startup and works alongside the founder on Product Development, Engineering, Team Building, and GTM strategy. What makes this interesting is that all of it happens before any conversation about equity or capital comes up.
The person behind the studio has spent more than 5 years as an Engineering Manager.
So naturally, a lot of the hands-on help leans towards the engineering side, especially for tech-focused SaaS products. On top of it, he helps founders put their teams together and sets up conversations with VCs from his own network.
The business model serves 2 audiences:
Underpinning all of it is Gyanoday, a free, no-fluff knowledge base of startup insights, built for founders, investors and anyone keeping a close eye on the early-stage startup world.
In July 2025, the studio was preparing to introduce itself through a LinkedIn launch which was planned for August. The LinkedIn assets, along with the website design in Figma, were ready. But back then, there was no website.
When the founder reached out to us on LinkedIn, that Figma had already been with other developers for three months, and nothing had been shipped. Which meant the studio was heading into its own launch with nowhere to send people.
He liked that approach and with that, we got started. Before getting into the development work, we first laid out the goals and what the project needed to achieve.
To address the above challenges, we took on the website from the ground up. The engagement covered:
The brief was pretty simple actually. The founder loved the design in Figma and wanted the website to look exactly the same when built. There were no specific targets for traffic or sales. He just needed a website that people could visit when the studio launched on LinkedIn, so they could see what the studio was all about.
To be honest, the hard part was the timeline. The August launch wasn't moving, and three months had already gone by without a single page going live.
For a venture studio introducing itself to founders and investors for the first time, showing up with a broken link or a placeholder page simply wasn't an option.
Almost every section of the Figma design had some kind of animation. From scroll-triggered reveals and card sequencing logic to SVG path animations and microinteractions. However, none of these animations had been prototyped.
That's partly because Figma has limitations when it comes to motion. So the designer wrote down what she was imagining for each animation instead. There were no references and no motion specs. It was just intent on paper.
On top of it, the final approval on this project sat with the designer. Which meant every animation we built had to match what the designer had in her head, even when it wasn't written down anywhere.
That challenge required someone who could read intent, turn it into motion, and still hit the date.
After our first call with the designer, we broke the project down into sequenced milestones. The hero section and footer came first, then the founders section, then the ventures module, and finally the knowledge base section. All of it was planned to be delivered within three weeks.
Each milestone was a shippable chunk. That means, if something was off, it showed up early instead of at the very end.
Whenever something in Figma was unclear, our developer took the initiative to figure it out. We worked out what the designer had in mind, built it, and showed the founder a demo. Most of the time the founder liked our version better than the original direction.
The most technically demanding piece was the four pillars animation.
The designer had originally suggested something else for this section. But during our conversations, the founder explained the idea behind the studio's four pillars, and he wanted them represented as a swastik. So that's what we built.
The swastik reveals itself as you scroll. We took the layered SVG from the original design file and built SVGs on top of it. Each arm is a separate masked segment that unmasks step by step as the user scrolls. And the timing of each arm is mapped to a specific scroll position using GSAP ScrollTrigger.
Getting the geometry right meant working through trigonometric calculations to define the sweep path for every segment. This one animation took 2-3 days on its own.
Next, we worked on the ventures card section. The cards move in a way that looks random, but every movement is carefully planned. Each card has a set path that decides where it enters from, how it moves, and where it ends up.
What looks like randomness on the surface is actually driven by carefully calculated positions and motion.
As far as the tech stack is concerned, the site is built on Next.js, with Tailwind CSS for styling. GSAP handles the scroll-driven reveals.
But wherever an animation could be done with CSS alone, like the hover effects on cards, we stuck to CSS. That's because every extra GSAP ScrollTrigger makes the page heavier, so we kept them to the minimum the design needed.
Additionally, we built two contact forms using React Hook Form and NodeMailer, so inquiries reach the team directly by email.
We also built reusable components for sections like the FAQs. That means, after launch, the founder could add new FAQs himself without coming back to us.
For analytics, we integrated Vercel Analytics, since the site is hosted on Vercel. It's free, and it gives the team basic visibility into page visits and which countries their visitors are coming from.
The full website, four pages with custom animations across every section, was delivered in about 4 weeks. That's the same Figma that had spent three months with other developers without going live.
At OhDamn!, we believe a website that looks extraordinary but loads slowly is worse than one that looks ordinary and loads fast. Slow pages get penalized by search engines. Moreover, users abandon slow websites, which means lost conversions.
For this studio, the risk was specific. The founders and investors it wants to reach could be opening the website on anything. Some will be on a high-end laptop with a fast connection, others on a budget phone with power saving turned on, and there's no way of knowing which.
So the website had to work just as well on both ends of that spectrum.
The more GSAP ScrollTriggers a page carries, the heavier it gets. And this design called for scroll-triggered animations in nearly every section, sometimes several of them firing as a single section. On a desktop with a fast connection, that works fine. But on a low-end phone with power saving on, it struggles.
On top of it, a lot of animations simply don't translate well to a phone screen. There isn't room for as many moving sections, and what feels smooth on a desktop can feel cramped and heavy on mobile.
The footer was the clearest example of this.
Its background animation used a different approach, one that would have been expensive to render in real time on every visitor’s device. Originally built with Three.js, the effect was generated dynamically at runtime. It worked well on capable devices, but became a performance bottleneck on less powerful ones.
We started by testing. We opened the site on low-end devices with power saving mode on and reduced frame rates, specifically to find where the experience broke down. This was part of the approach we had discussed with the founder on Day 1, so it was never an afterthought.
Then, we made the site aware of the device it's running on. If the visitor is on a phone, a separate, lighter animation is triggered.
For example, the four pillars swastik has its own mobile animation. Further, the menu and the wordmark resize for the smaller screen, and in a few sections the content shifts up so it fits better.
Meaning, the animations look nearly the same on mobile, but the chunk size is smaller and the rendering cost is significantly lower.
The footer called for a different approach.
We built the animation in Three.js, rendered it once, and exported it as an optimized GIF. Instead of generating the effect on every visit, we embedded the GIF directly into the website. That means, the visitors saw the same visual, but their devices no longer had to do the rendering work. This eliminated the animation’s runtime rendering cost entirely.
For content, we structured everything into JSON files, with separate files for each page and section. Every piece of copy, image, and icon was accounted for. We also built parser layers on top of it. So whenever the team is ready to move to a CMS, it can be plugged in through an API call without rebuilding the site.
The site ran without any degradation across the low-end devices we tested with power saving enabled. For the next couple of months after launch, we stayed in touch with the founder and offered 45 days of post-launch support.
However, the website didn't face any issues and he was also able to update the content on his own.