01Question02Build03Use
Making things.
Making sense.
Becoming.
I’m Robert. I build software, follow questions, and write about what I discover along the way.
An idea becomes
something useful.
I turn questions into products, then take responsibility for what happens when people use them.
Give it a purpose.
Then give it a life.
Product, engineering, and the responsibility
of staying with what you build.
MY CURRENT FOCUS · CLOSED BETA
rootmail.
Business email.
Every customer’s identity.
A record of what happened.
I designed, built, and now operate the platform, from the API and dashboard to the infrastructure and developer SDKs.
01 / IDENTITYONE PLATFORM. MANY CUSTOMERS.
The platform is shared.
The identity is theirs.
Your application
rootmail.One workspace
ACustomer ATheir domain & signing key
BCustomer BTheir domain & signing key
Workspaces and sub-tenants keep sending domains and signing keys distinct, whether you serve one business or many.
Architecture, simplified.02 / EVIDENCEFOLLOW THE MESSAGE.
“Sent” is just
the beginning.
- 01Request acceptedThe platform receives the request.
- 02Queued for sendingThe work moves into the sending pipeline.
- 03Provider event recordedKeep the signal and its source.
- 04A reply, when it arrivesAnother part of the conversation.
I built the record around what the system observes. A provider event is evidence; it isn’t a promise that someone read the message.
An explanatory lifecycle, not live message data.03 / OWNERSHIPBUILD IT. STAY WITH IT.
The whole product.
Including what’s underneath.
01The interfaceDashboard & customer experience
02The contractAPI, authentication & SDKs
03The engineQueues & sending infrastructure
04The responsibilityOperations, tracing & improvement
The product is the promise. Engineering is how I keep it, through the first build and everything that follows.
BEFORE ROOTMAIL / A FOUNDER’S PERSPECTIVE
The work matters.
So does working together.
Samuel MarseilleFounder, Oneshot TranslationFrom his recommendation · June 27, 2026
He treated our platform as if he owned it, because for all practical purposes, he did.
His infrastructure choices — Docker, CI/CD pipelines, proactive monitoring — reflected an engineer who thinks in systems, not just features.
For a non-technical founder, having an engineer who combines full autonomy with clear communication is invaluable — and rare.
We worked together from December 2024 to December 2025.
The platform behind these wordsBuilt. Tried.
Carried forward.
Oneshot
Translation.
A document translation business, built into a complete platform. Customer experience, automated processing, deployment and reliability.
~60%less turnaround time
99%+annual uptime
Inside the work
I built the frontend and backend, integrated third-party services, and automated document ingestion with AWS Lambda. Docker, CI/CD and monitoring supported the platform in production.
See this chapter in my journeyIntelligent
Writing Assistant
An experiment in making writing tools more useful, built with Python, FastAPI and React.
Explore the projectCloser to
the machine.
A custom printf in C. Learning systems by building the foundations myself.
Explore the codeWORK WITH ME
Got something
to build?
Bring the problem. We’ll work out the shape.
Software that holds up. Words that make it clear.
Or explore a starting point.
“He treated our platform as if he owned it.”
Samuel Marseille · Founder, Oneshot01 / BACKEND APIS
An idea needs a backbone.
Your product needs more than endpoints that work on a good day.
A Node.js / TypeScript and PostgreSQL API, with authentication, validation and a clear handover.
- A database shaped around your product
- Tests and API documentation for the agreed scope
- A clean repository with setup instructions
From $150USD · scope agreed firstStart this project
View current packages on Fiverr
Scope & common questions
- $150One resource + authentication
- $350Multiple resources, tests + docs
- $700Backend, queues + webhooks
Starting prices in USD. Final scope, timing and quote are agreed before work begins.
Can you work with an existing backend?
Yes. Share the stack and the part that needs work. We’ll agree whether extending it or building a separate service makes more sense.
02 / AWS & DEPLOYMENT
Deploy without the deep breath.
Manual releases make every change feel bigger than it should.
A repeatable route from your repository to production, with infrastructure and visibility that fit your app.
- CI/CD for the way your team ships
- AWS setup appropriate to your workload
- Monitoring and handover in the agreed scope
From $120USD · scope agreed firstStart this project
View current packages on Fiverr
Scope & common questions
- $120CI/CD for an existing app
- $300Compute, database + storage setup
- $600Monitoring, Terraform + handover
Starting prices in USD. Final scope, timing and quote are agreed before work begins.
Are AWS charges included?
No. Hosting stays in your own account, and usage is billed by AWS. We’ll discuss the infrastructure and expected costs before setup.
03 / DOCUMENT WORKFLOWS
Let the repetitive work go.
Someone is still downloading, moving and processing the same documents by hand.
An AWS Lambda workflow that connects the steps, handles failures and gives people their time back.
- A map of the current manual workflow
- Automation for the agreed document steps
- Error handling and an understandable handover
From $150USD · scope agreed firstStart this project
Scope & common questions
- $150One Lambda automation
- $350Multi-step pipeline + error handling
- $700Full system, monitoring + dashboard
Starting prices in USD. Final scope, timing and quote are agreed before work begins.
Do you need real client documents to begin?
Start with a description and anonymised examples. We can agree how sensitive documents should be handled before sharing any.
04 / RETRY-SAFE SYSTEMS
A retry shouldn’t happen twice.
A timeout becomes a second job, a duplicate webhook or an invoice nobody expected.
Review the retry paths, then add idempotency and duplicate handling where they matter most.
- A review of failure and retry behaviour
- An implementation matched to the agreed scope
- Tests that exercise duplicate requests
From $100USD · scope agreed firstStart this project
Scope & common questions
- $100Retry-hazard audit + report
- $250One critical path made retry-safe
- $500A scoped codebase retry-safety pass
Starting prices in USD. Final scope, timing and quote are agreed before work begins.
Is this only for payments?
No. Background jobs, webhooks and other side effects need safe retry behaviour too. The first step is identifying what must happen only once.
05 / ARCHITECTURE REVIEW
Different services. Still tangled?
A small change needs three coordinated deployments. The boundaries aren’t doing their job.
A practical review of coupling and ownership, with a prioritised explanation of what to change first.
- A review of your diagrams or architecture notes
- Specific risks tied to your system
- An actionable written review
From $120USD · scope agreed firstStart this project
Scope & common questions
- $120Written architecture review
- $300Review + a walkthrough call
- $600Remediation plan + follow-up
Starting prices in USD. Final scope, timing and quote are agreed before work begins.
Do we have to rewrite everything?
A review is meant to help you choose. It can identify small changes, clarify trade-offs or show why a larger change is worth considering.
06 / MVP BACKENDS
Get the idea into someone’s hands.
You have something to test with users. You need a working foundation, not an endless build.
A scoped product backend with an API, database, authentication and a route to deployment.
- A clear scope and agreed milestones
- Demos as the build takes shape
- Documentation and a practical handover
From $800USD · scope agreed firstStart this project
Scope & common questions
- $800Single-service MVP
- $1,800Multi-service, auth + admin basics
- $3,500Platform, queues + monitoring
Starting prices in USD. Final scope, timing and quote are agreed before work begins.
How long does an MVP take?
That depends on the scope and integrations. Share what the first version needs to prove, and we’ll agree milestones and timing before work begins.
07 / TECHNICAL WRITING
Give developers a reason to stay.
Your product has something useful to say. Generic content won’t say it well.
Tutorials and technical deep-dives grounded in engineering, with research, code and a point of view.
- An outline aligned with your audience
- Clear explanations and relevant code examples
- A finished article for the agreed brief
From $80USD · scope agreed firstStart this project
Scope & common questions
- $80A 1,200-word tutorial
- $200A 2,500-word deep-dive with code
- $400A three-article series
Starting prices in USD. Final scope, timing and quote are agreed before work begins.
Can you match our product and editorial voice?
Share your audience, product docs and a couple of examples you like. We’ll agree the angle and outline before the full draft.
08 / DEVELOPER DOCUMENTATION
The first integration should feel possible.
Developers shouldn’t have to open a support ticket to get their first request working.
API references, quickstarts and integration guides that connect the concepts to working examples.
- A path from setup to the first useful result
- Examples aligned with your API or SDK
- Clear reference and troubleshooting content
From $100USD · scope agreed firstStart this project
Scope & common questions
- $100One API quickstart
- $250API reference + developer guides
- $500Docs content, tutorials + SDK examples
Starting prices in USD. Final scope, timing and quote are agreed before work begins.
What do you need to get started?
Your current docs or API specification, a safe test environment and the audience you’re writing for. We’ll scope the pages and examples together.
Have a starting point?Tell me what you’re building.
A little context.
A real beginning.
An unfinished idea is enough. Tell me where you are and what would make a difference.
- 01 Send your brief here.
- 02 We work out the fit and scope.
- 03 Agree the plan before work starts.
This is an enquiry, not a booking or payment.
Some questions
become essays.
Software, possibility, and the very human
business of figuring things out.
A few places to begin
THE POSSIBLEThe Developer codes
The Moment Starship Becomes Real.
Read the essayTHE PRACTICAL
The Developer codesIf-Match:
Read the essay
If-Match:
two curls, one 412.
Read the essay
THE PERSONALOur Curious MindsHe lives in you…
Read the essay
He lives in you…
in the simplest things.
Read the essayFind your kind
of conversation.
Pick a place that feels like you.
I’ll meet you there.
SubstackBuild. Write. Explore. Become.
Stay for the longer story.
Essays, questions and the work of becoming. Three publications, each with its own point of view.
Choose your notebookSubscribe here, just below.
LinkedInOdinaka Robert Nnamani
Build a professional connection.
The engineer, the founder, and the thinking behind the work. A place to connect around what we could build together.
X@paschals_robert
Join the thought while it’s forming.
A shorter route into the conversation: ideas, questions and the people thinking about what comes next.
X may ask you to sign in.
Medium@robertpaschal
Follow an idea a little further.
Another home for my writing. Find a story, take your time with it, and follow along on Medium.
DEV@robertpaschal
Get into the details.
Software, implementation and learning through the work. Find me in the developer community and join the discussion.
01 / 05
Different notebooks.
The same curiosity.
Choose the part that speaks to you.
Let the next piece come to you.
01 / THE WHOLE JOURNEYPascal.
Build. Write.
Explore. Become.
The home for what I’m building, what I’m learning, and who I’m becoming.
Explore the notebook
02 / UNDER THE SURFACEThe Developer
codes.
Understand the tools.
Imagine what comes next.
Software, emerging technology, and the ideas changing what we can build.
Read the publication
03 / THE HUMAN PARTOur Curious
Minds.
Stay open.
Follow the feeling.
Stories, reflection, and the small things that help us understand ourselves.
Read the publicationSignups are handled by Substack. Unsubscribe whenever you like.
Somewhere
in the middle.
I don’t think we become
ourselves all at once.
I studied biological sciences, trained in software engineering, built products for other people, and started building one of my own. The route hasn’t been a straight line. The curiosity has stayed.
01 / THE CURIOSITY
A way of looking.
Biological sciences taught me to look closely at systems. Software gave me a way to build them.
Follow the path02 / THE CRAFT
A way of making.
I care about the whole product: the experience on screen and the infrastructure nobody should have to think about.
See it in the work03 / THE REFLECTION
A way of understanding.
Writing is where I take the questions left over: ambition, creativity, failure, and building a life that feels like my own.
Find it in the writingA home for a life
in progress.
Pascal began with a question:
what if I shared the becoming, too?
A path. A point along it. Not an arrival.I build things to make an idea useful. I write to understand what the work asks of me. Pascal gives both a place to live — including the uncertainty.
01The line keeps going.
The flowing mark reminds me of a path. My own has moved from biological sciences into software, from building for others to building Rootmail. A turn in the path doesn’t erase what came before it.
02One home for all of it.
The P carries the Pascal name. I didn’t want the technical work and the person doing it to live in separate boxes. Software, creativity, ambition, and the questions left after the laptop closes belong in the same story.
03Here. Still on the way.
The little blue dot is a point along the path. It gives the mark a place to pause without making that place the finish. I don’t need to have everything figured out before I can share something worth reading.
“You don’t have to wait until you’ve arrived
to have something worth sharing.”
A path.
Always unfolding.
ALX Africa
Software engineering · Training & projects
Learn it.
Build it from scratch.
From C and a UNIX shell to APIs, databases and distributed systems. A foundation built through the work itself.
One of those foundations JUL 2023 — AUG 2024Oneshot Translation
Full-Stack Software Engineer
A whole platform.
A business depending on it.
Working directly with the founder, I turned business goals into a complete product, then took care of it in production.
The founder’s perspective DEC 2024 — DEC 2025Outly Technologies
Chief Technology Officer
Build the product.
Listen to the market.
I led engineering for a consumer marketplace. We built, but traction didn’t follow. That chapter belongs here too.
Making software is one part of finding something people need.FEB — JUN 2026Rootmail
Founder & Principal Engineer
An idea of my own.
A responsibility I chose.
Building and operating an email platform through a closed beta. Product, engineering and the next decision, all in the same hands.
Back to what I’m building JUN 2026 — PRESENTStill becoming.
The detours belong in the story, too.
Still a way forward.
01Change direction.Biological sciences to software
02Learn from the attempt.Outly, and the questions it left
03Begin again.Rootmail. Writing. The next question.
FROM THE CHANGE OF DIRECTIONBegin before
Begin before
you feel ready.
Biological sciences wasn’t the end of my story. Learning software meant being a beginner again — and finding another way to follow the same curiosity.
FROM THE THINGS THAT DIDN’T LANDLet the attempt
Let the attempt
teach you.
At Outly, we built a product; traction didn’t follow. That experience stays with me. Building something and finding something people need are different kinds of work.
FROM BEGINNING AGAINKeep making.
Keep making.
Keep making sense.
Rootmail gives the next attempt a shape. Writing gives me a place to examine the decisions, doubts, and discoveries along the way.
Stay for the next chapterWhat could we
make happen?
A team. An idea. A question you can’t shake.
I’d like to hear it.
Independent work.
Shared possibility.
If something I build or write has meant something to you,
you can be part of what comes next.
Buy Me a Coffee
A little fuel for
the next idea.
For the build that saved you time, or the essay that stayed with you. A small thank-you can be encouragement to keep making.
Follow along here. Tips aren’t open yet.
Patreon
Give the work
room to grow.
Back the time behind the work: the experiments, the rewrites, and the ideas worth staying with. A way to support the long game.
Coming soonFollow the journey
Bring someone along
Good work travels
person to person.
If something here stayed with you, pass it to someone who might need it. Or join a notebook and be part of what comes next.