about
i work across the seams.
difficult work rarely belongs to one function. operations knows the exceptions. legal owns the boundary. engineering owns the runtime. finance sees the cost. product sees the person doing the work.
the role
one person carries the whole loop.
hi, i’m roux. i have worked across data, product, engineering, finance, company-building and operations. i have founded companies and led one as coo.
the range matters because the result belongs to several teams at once. that often means nobody carries it from the first operating problem to the working system. i do.
how the work starts
real cases before feature lists.
we follow recent examples from the first incoming event to the final action. who touched it? what did they need to know? which figure had to be exact? when did the deadline really begin?
the answers reveal the true system boundary: what may be removed, what must be deterministic and where a person must remain responsible.
every step removed is a step nobody has to perform, maintain, audit or explain later.
one complete loop
choose. draw. build. prove. transfer.
choose
one painful workflow, one team, one owner and one measurable result.
draw the boundary
separate model work, exact rules and human responsibility.
build
connect the real channel and return the decision where the team already works.
prove
run historical and live cases, including the ways the system can fail.
transfer
name the owner, document the system and remove me from daily operation.
selected evidence
the work is measurable.
removed from the cost base of a €23m arr platform.
downloads grown while reducing burn.
a business bootstrapped without outside funding.
the measure of success
my absence becomes uneventful.
the organisation keeps the infrastructure, keys, rules, records, tests, fallbacks and named responsibility. dependence is not the product. ownership is.
connect