Two ways in. Both reach an engineer.
Pick whichever suits how you think. A short call is faster if the problem is fuzzy; a written brief is better if you already know the shape of it.
Book an architecture call
Straight into an engineer’s calendar.
- 1What you are trying to changeFive minutes on the actual business problem, not a feature list.
- 2How we would approach itA specific architecture, named trade-offs, and where the risk sits.
- 3What it realistically costsA budget band and a timeline you can take to whoever signs off.
Scheduling by Cal.com · reschedule or cancel any time
Write us a brief
Composed in your own mail client — nothing is stored on this site.
Goes directly to hello@folrik.com. An engineer reads it, and you get a reply with a first take usually under 12 hours.
Three steps, no funnel.
You hear back from an engineer
Usually under 12 hours. Not an account manager, and not an automated sequence.
We tell you what we would build
A specific approach with the trade-offs named, plus an honest signal if we are the wrong team for it.
You get a number to plan against
A budget band and a timeline. If you want it firm, that comes out of the five-day architecture sprint.
What makes a brief useful
None of this is required. It just means the first reply contains an answer instead of five clarifying questions.
- What is broken, slow, or manual right now
- What good looks like, in a sentence
- Your current stack, if there is one
- Rough budget range and target date
- Anything already written down: docs, repos, screenshots
When we are the wrong call
We would rather say this here than take a discovery call and disappoint you at the end of it. For most of these, a specialist freelancer is a better and cheaper fit.
- Single-page marketing sites and template installs
- Ongoing content, SEO, or paid media work
- Fixed-scope work under $1,500
- Anything requiring us to bypass a platform's terms