Daniel Raison
Joined November 2026
Follow. Sign in to follow Daniel Raison
Want to read what Daniel Raison writes next? Follow them for new founder stories by email.
Products Daniel Raison founded
Pickode
Turn any website into clean, editable code
- Browser Extensions & Plugins
- Growing
- Italy
- 0 votes
Interview
- What problem are you solving, and who has it?
- Turning a section you like on a website into something you can actually edit in your own project. Today that usually means copying computed values out of DevTools, losing the breakpoints and hover states, and rebuilding it by hand.
The people who hit this most are web designers, freelancers and small agencies, especially those building with Bricks, Elementor or Webflow. They migrate client sites, work from references and reuse layouts all the time. Front-end developers who want clean React, Tailwind or Vue code from a live page have the same problem.
Pickode reads the CSS the author wrote, keeps the responsive rules and hover states, and exports the section as code or as native builder elements, so the starting point is close to the original and stays editable. - Why did you start this company?
- It isn’t really a company yet. It’s a product I build on my own, alongside my work as a web developer for clients.
I started it because I kept running into the same problem in that work: taking a section from an existing site and rebuilding it in WordPress or in code took far longer than it should, and the tools I found copied the wrong CSS. I wanted something that read what the author actually wrote and gave me a starting point I could edit with the builder’s own tools.
Once it worked for my own projects, it felt worth making it good enough for other people with the same problem, and selling it so I can keep working on it. - What was the hardest moment so far, and how did you get through it?
- Probably the day the first serious tester sent his results. He’d copied a site built with Elementor into Bricks and Webflow, and in Bricks the buttons had turned into plain text and the mobile layout was broken. His message ended with something like: why wouldn’t I just use an AI tool and rebuild it myself?
That stung, because he was right. The tool was supposed to save him time, and on that site it didn’t.
What got me through was treating it as data instead of a verdict. I opened his Bricks page and the original side by side and measured what went wrong: zero real buttons, a few hundred lines of CSS that did nothing, rows that never stacked on mobile. Each problem had a specific cause in the code, and specific causes can be fixed. Over the next days I rebuilt the Bricks export around native elements, and his site became one of the tests every new version has to pass.
I also thanked him properly. Feedback that honest is rare, and it’s worth more than any launch. - What are you most proud of?
- That it reads the CSS the author actually wrote. It sounds like a small technical detail, but it’s the hardest part of the whole product and the reason the rest works. Most tools take the shortcut and copy what the browser computed, because it’s easier. Pickode follows the real stylesheets, the media queries, the hover states and the variables, and turns them into something you can keep editing.
I’m also proud that it runs entirely in the browser. There’s no Pickode server and no account to start, so the sites you inspect and the code you export never pass through me. - What would you tell a founder starting today?
- Find one person who will use your product on their own real work and tell you honestly what broke, and do it as early as you can. My own tests said Pickode was ready. The first real test on a site I’d never seen said otherwise, and it was the most useful thing that happened to the project.
When the feedback hurts, don’t argue with it. Open what they saw and measure it. “It’s bad” turns into a list of specific causes, and specific causes can be fixed.
And read the store rules before you write your listing, not after the rejection. - What is next for you?
- The next few weeks are about making the copy faithful on more real sites. I’m putting every new export through the sites testers send me, at desktop, tablet and mobile widths, and fixing what breaks before adding anything new.
On November 17 I’m launching on Product Hunt, so I’m also looking for more people who build with Bricks, Elementor or Webflow and want to try it on their own projects. If that’s you, write to me.
Longer term, I’d like Pickode to cover a whole page, not just one section, and to turn code from AI tools into native builder elements.