Six weeks.One builder.Your first release.

I own definition, product design, engineering, QA and handover. Inside your private client room, every decision and Friday preview stays visible — watch it take shape.

W01W02W03W04W05W06release
Before the process · check the shape

Does your product fit?

Best for a validated problem, a decisive owner and a first release that can become valuable in six weeks.

You bring
  • the problem
  • domain knowledge
  • customer evidence
  • access to users
  • authority to decide
I own
  • definition
  • product design
  • engineering
  • quality
  • release
Not included
  • customer acquisition
  • paid marketing
  • social
  • ongoing content
  • sales
sector 02 · protocol

Blueprint first. Then the build.

A product manager's real job is deciding what's out. The Blueprint is five days of exactly that. We define the right first release, write acceptance criteria you approve and fix the build price. You can stop there with a product definition you keep, or continue into the six-week build.

01 · five days · before the build
Blueprint
$5kcredited in full toward the build

Continue into the build and the full $5k becomes part of the $35k+ total—not an extra fee.

  • First release: what's in, what's out
  • Journeys, architecture, risks
  • Acceptance criteria you approve
  • A fixed build quote
  • Your room, already populated
02 · six-week build
The build
from $35k totalincludes the Blueprint · build balance from $30k · milestone payments

One fixed engagement covering product definition, design, engineering, quality, production release and handover.

  • Production-ready first release
  • Something clickable every Friday
  • Private room: progress, decisions, questions, previews
  • Fixed scope and price before the build begins
At handover, you own
Production releaseRepository, infrastructure and accountsArchitecture and operating documentationComplete decision record30 days of defect fixes
1Approved release, architecture, clickable direction
2Core journey with real data
3The differentiating capability, end to end
4Integrations, payments where required
5Edge cases, admin, monitoring
6Production-ready release, docs, handover
sector 03 · the room

Progress you read, not chase.

The first thing I design on any build isn't a screen. It's your experience of the build. Every project runs inside a private client room: a published record of what changed, what's moving, what needs you and what becomes ready. You get the signal without inheriting the machinery.

acme · client roomlive
01 / 04What changed.
week 3 of 6preview · friday
active outcomein build

Organization invitations

nowReviewing the invitation flow
nextResolve the missing expiry rule
previewFriday
today2 latest updates
review

Review caught one missing expiry rule.

The edge case is contained. One product decision will settle the behavior.

progress

Invitation creation is complete.

Creating, sending and accepting an invitation now works end to end.

illustrative client feed · published progress only
sector 04 · methodwhere coherence gets lost

Early products don't fail on code. They fail on handoffs.

Not because those disciplines are unnecessary — because responsibility for a still-forming product gets divided across too many handoffs. I've held every one of those seats. Now I own the thread across all of them.

I've held each seat.

not my hatsmarketing · social · brand identity · pitch decks · fundraising · solidity — I'll tell you who to call.
                                                                            
                             ,.`...''''''`..``_                             
                         _...`_$   `'''''.  $_`.`.'                         
                      _...'$ .:-+=xtooootx=+-,`  -`. `                      
                    `..`$ '_*x%#@@$$$$$$$$$@#%t=~,. ~...,                   
                  `. ` .,*t&@$$$$$$$$$$$$$$$$$$@#%i+: $.'.                  
                 . . ._i%#@@$$$$$$$$$$$$$$$$$$$$@@@#o*: ' .                 
                . : ,i&@@@@@$$$$$$$$$$$$$$$$$$$$$@@@@@o~.+.`                
               ,.'.~%@@@@@$$$$$$$$$$$$$$$$$$$$$$$$$@@@@&+.`                 
               .. -&@@@@@$$$$$$$$$$$$$$$$$$$$$$$$$$$@@@@&_ .`               
               . 't@@@@@@@@@$$$$$$$$$$$$$$$$$$$$$$$$@@@@@x`~`               
               . -#@@@@@@@@@$$$$$$$$$$$$$$$$$$$@@@@@@@@@@#_ .               
              ,..*@@@@@@@$$$$$$$$$$$$$$$$$$$$$$$$$$$$@@@@@* .,              
              _``x@@@@&%ooooooo%&@@@@$$$$@#%%oooottt%#@@@$x..-              
              'i`t@@&i~-_,::::::,+%$@@@$#i_:::::::,,_~t@@@t`_:              
             ,` 'o@%+=xx=~-__--~+i#@@$$$@%=+~--_-+itti+i#@o' '              
             ,..'++_,___,,,,,,,,_-i%###o%=__,,:,,,,____,~+~`..              
          .$`-:.:,_~***+++++~---_::_~+_,_:,---~+++++*=*+_,,`.:~` `          
          .-`_,.`,-ox*+~++~~~+*xi+,`'-'`'_*i*+~~~~++~+it=,:..__`o`          
          . _+=*::+&x+-_*ti**xxx&%-:=&%~:*%t=oi+*xx~-~i%t,::==+_ .          
          . -*+=i:-##o=+=xxxxxo&#&__&@$%,*##%xxiix=**x&@=::=i++_ .          
          .,:**~+:,o@@&x===it&@@@i:~@@@@~,o$@%xii==it#@#-,:++==,$`          
          `..~***,:+#@@#&%%&@@@$%_:=@@@@i:-&$$@&&%&#@@@=,-,*ix+.`.          
           `:`***_,_+xo%&####&%i__-t@@@@%-_-x%#####&%t*,+~,*i='_ ,          
           `  _i=-:+~---~~~~~-_-*it@@@@@@o*+----~~~----*t,-*i_  .           
            .. ,=i:+oxii====ixo&xo&%&##&%#oi&oxii===ixo#=,=+_ ..            
            ,..$'==:o##&####@@$@i=**ixx=+*=x$$@@##&###@%,==`#.`'            
              .  :,`-%@@@$$@@$@#%=~~~**~-~*%#@$@@@@@@@&~`,'  .              
               . :x._=%@@@@@#%i***+-,**,_+***i%@@@@@@%=,.,: .               
                 `'.,*i#@@#x=+~+~~~+iii=+~~-~~~it#@@&=*:. `                 
                 '..'*=%@@x*~-++*=ixxxxxxii*+~-~*t@@oi*'..:                 
                 .```,+i&&t=i%####@#oi=t#@####&i*i%%x+,...'                 
                 ~ .`.:+ix%t@@@@@@@#*::_o@@@@@@#xii=~:.`..                  
                  : `..:-=txo&#@@@@t,:::-&@@#&&tii*-'.`. '                  
                   `..,.:_+*=xt%%t=*_,,,_xt%%tx==+,`. ``_                   
                    ~`..-+,_=ixtx=xi~~_~ittttx=*-_-' '`-                    
                      ..*o*__+=tiixi**-=xttxx=-,-ix' '                      
                     ~..=@t*~-_*===i***=ixi=+__+x#o' '                      
                     `..=@#t*+*-_-~++~~+*+-,-++t#@%' `                      
                     :'`x@@#%*+=*~-__,,__-~**+o@@@&: .                      
                     . 'o&@@@#i=ii========i=+t@@@@#_ .                      
                   .:. _&o@@@@#xtxii===iiii*o@@@@@@* .`.                    
                 ,  ` .-#x#@@@@%o#&%oooo%&o%@@@@@@@*. :..'                  
                 ,  .:~-=t%@@@@@o#@@@@@@@#o@@@@@&&i-~,`..'                  
proc/01product

Ran a business, not a backlog.

Founded and ran a media company, turned a client project into a platform, shipped my own since.

Read the experience →

Ran a business, not a backlog. Founded and ran a media company — IGN, PCMag and AskMen in Portugal — selling the ads as well as running them, hiring the team, owning the P&L. At the agency I was the product owner for a dozen client projects, directly with the client, and turned one of them (Tetra Pak) into a platform serving Pepsi, Merkle and others. Built, priced and shipped my own products since: Waveloom, ramp.sh, two apps on the App Store. I scope around user value and commercial reality.

proc/02design

Flows before pixels.

Half of 50+ agency projects designed myself; SuperRare's UI from primitives; two apps shipped.

Read the experience →

Flows before pixels. Designed roughly half of the 50+ projects I shipped at the agency myself — no designer in the loop — including the agency's own site, three times over. Rebuilt SuperRare's marketplace UI system from Radix primitives. Designed and built two native apps people downloaded. I'll draw the flow before I draw the screen, and I'll change the screen when the flow is wrong.

proc/03quality

Survives a bad day.

Burn-once codes at scale, idempotent execution, server security, live moderation.

Read the experience →

Survives a bad day. A multi-client QR platform generating thousands of burn-once codes per batch for live enterprise campaigns. An idempotent execution graph under Waveloom. Server orchestration with a real security surface at ramp.sh. AI-assisted moderation on a live community at Right Click Save. Six years as the person accountable when a client's launch broke at 9am. I break it before your users do.

proc/04engineering

Twenty years in production.

Laravel to Next.js to Solana to AI agents; agentic three years; documented for handover.

Read the experience →

Twenty years in production, from PHP shops to Solana programs to AI agents — Laravel, Node, Next.js, React Native, AdonisJS; APIs, CLIs, MCPs; the only chain I'll claim end to end is Solana, and I've shipped it. Fully agentic development for three years, one of the first fifty people on Cursor. Built and documented so your next engineer takes over cleanly, not archaeologically.

not my hatsmarketing · social · brand identity · pitch decks · fundraising · solidity — I'll tell you who to call.
proc/05 · deliveryOne accountable owner.

Product judgment, design, engineering and quality stay in one continuous context.

sector 05 · evidence

Numbers, not adjectives.

Engineers don't get to say “trust me.” They get to point at what's running. Waveloom proves product and engineering; SuperRare proves design and performance; Appetite proves delivery; IGN proves I can run a P&L. I choose established, maintainable tools around your product and your future team, not my résumé — and hand over a repo your next engineer can take over cleanly.

operator · the product engineer behind it

Tiago da Silva

20 years shipping to production. Ran the business too.

  • Founded and ran Skift — IGN Portugal, then PCMag and AskMen under Ziff Davis licence: ads, creatives, ad sales, hires, team and P&L, 2014–19.
  • Six years at Appetite Creative as first engineer and tech director — the person clients chased for status across 50+ projects, which is why the room exists.
  • Built the AI agent behind Amy end to end and solo-built Waveloom, an AI orchestration product with 10+ providers and Stripe billing.

Dubai and Portugal, any timezone that's awake. Written-first, async-friendly; you work directly with me and I reply within one business day.

For six years, Tiago was the engineer our biggest clients asked for by name. Hand him something vague and he hands you back what actually matters — decided, built and shipped, with everyone knowing exactly where things stand. I watched him do it across fifty-plus projects.
Jenny Stanley · Managing Director, Appetite Creative
The hiring plan
  • weeks disappear into hiring, reinterpretation and re-planning
  • status lives in Slack scroll and Friday emails
  • decisions live in someone's memory
several commitments · months of coordination · no single owner
One product engineer + a room
  • one owner from plan to handover, week 1 to week 6
  • progress is something you watch, not ask for
  • every decision on record, with its reason
from $35k total · six-week build · one accountable owner
digital self · online 24/7

Ask me before you ask me.

Mafra knows the offer, the work behind it, how I build, and where the edges are. Use my digital counterpart to pressure-test the fit before spending twenty minutes on a call.

Instant answers. No form, no calendar, no sales script.

sector 06 · qa

What could go wrong?

A tester's job is to ask the awkward questions before the user does. So, before you book anything, here are the ones I'd ask me.

product judgmentdesignqualityproduction engineeringdelivery & handover
sector 07 · contact · a little context, then twenty minutes

What are you trying to ship?

Share a little context when you book. In twenty minutes, I’ll ask about your users and give you a clear next step: Blueprint, not yet, or “you don’t need me — here’s who you need.”

20 minutes · no deck required · no sales theatre
Book the fit check Prefer async? Send a deck or Loom to tiago@mafrasil.com