2012
RTW opens in Reston.
Jeff starts the studio after Booz Allen Hamilton, with a small client base and a practical focus: solve the technical problem, then stay close enough to support it.
Who we are
Digital engineering
EST. 2012
We build systems we are willing to support.
Reston Tech Wiz is a senior digital engineering studio in Reston, Virginia. Since 2012, we have built and supported websites, software, dashboards, integrations, AI workflows, and custom systems for clients who need practical technical judgment before and after launch.
Founded
2012
Core work
Web / software / support
Engagements
Builds / rebuilds / retainers
Operating style
Scope first / support after
// how we got here
Small studio advantage.
Reston Tech Wiz started after founder Jeff Schreibman left Booz Allen Hamilton, where he spent five years as a high-tech Senior Consultant. That background shaped the studio from the beginning: practical engineering, clear communication, and a bias toward systems that keep working after the first version ships.
Since then, RTW has grown carefully. The studio is large enough to handle serious web, software, dashboard, AI, mobile, integration, and support work, but still small enough that clients are not passed through layers of account management before reaching the people who understand the system.
That is the advantage of a focused engineering studio. You get senior technical judgment, direct access, and personal service without the friction of a large agency structure. Reston Tech Wiz brings enterprise-level discipline to digital work that still needs to feel close, practical, and accountable.
That is the whole pitch, really. We are senior engineers who decided to stay small, stay close, and stay in the work.
2015
First production platform ships.
A scheduling system for a DC-area logistics client moves RTW from project work into systems clients rely on every day. Still live today.
2018
The studio becomes a team.
RTW hires its first full-time engineers and moves into Winterport Cluster, expanding the work without turning it into a large-agency model.
2021
Support becomes part of the model.
The retainer approach is formalized so shipped systems have a clear path for updates, fixes, improvements, and real engineering context after launch.
2024
Design and product become part of the build.
RTW adds deeper product and interface work, because serious systems need more than code: they need flows, structure, usability, and scope discipline.
Today
Same standard, broader scope.
RTW now works across web platforms, WordPress, mobile apps, dashboards, AI workflows, integrations, custom systems, signage, hosting, and long-term support.
The working principles behind RTW.
Our values are not decoration. These are the principles that shape how we scope, build, launch, and support the work.
01
Senior people stay close to the work.
The people making the technical decisions stay involved from scope to support.
02
Launch is not the finish line.
Real work starts when users, updates, edge cases, and business changes arrive.
03
Durable beats fashionable.
We choose tools and patterns for the job they need to survive, not the trend they came from.
04
Scope is a form of respect.
Clear scope protects the budget, the timeline, the work, and everyone depending on it.
// Who holds the system
The right people at the messy parts of the system.
Good digital work needs more than implementation. It needs scope, architecture, interface decisions, infrastructure, integrations, and support thinking in the same room.
Founder
#001
Jeff
Big ideas, big energy, and somehow still finds time to ask "quick question?" before changing the whole plan.
Quick question. Probably not quick.
Vision
Strategy
Client calls
Ops
Numbers
#002
Andrew
Keeps the numbers clean and the rest of us financially supervised. Basically the reason our ideas do not bankrupt us.
Great idea. Show me the spreadsheet.
Finance
Budgets
Reality checks
Prototyping
PM
#003
Niina
Turns chaos into timelines and "almost done" into actual done. The calm voice before every deadline storm.
Almost done needs a date.
Planning
Delivery
Follow-ups
Event systems
Dev
#004
Valentin
Builds things that work, then quietly makes them work better. Probably already fixed the bug you are about to report.
Fixed it while you were typing.
Backend
Systems
Debugging
Writing
Dev
#005
Stefan
Solves complex problems with suspiciously calm energy. If the code is on fire, Stefan is already holding the extinguisher.
It is fine. I found the cause.
Architecture
Fixes
Code calm
State machines
Jira
#006
Slava
Knows every ticket, every status, and every excuse. Jira does not scare him - Jira listens to him.
If it happened, there is a ticket.
Jira
Workflow
Status truth
MQTT
Dev
#007
Kashif
Builds clean React interfaces and extracts useful data from places that were absolutely not designed to share it politely.
The data is there. It is just hiding.
React
JS
Web Scraping
Dev
#008
Ana
Moves comfortably between mobile screens, web pages, and JavaScript surprises. If it works on three devices, Ana probably had something to do with it.
One codebase, many ways to break it.
React Native
Next.js
JavaScript
Dev
#009
Andrei
Turns complex front-end requirements into structured, typed, styled systems. Somehow makes TypeScript and SASS feel like they agreed on the plan.
The interface is responsive. So is the code.
React Native
SASS
Next.js
TypeScript
Dev
#010
Daniel
Speaks fluent modern stack and legacy stack, which means he can fix the new thing, the old thing, and the mysterious thing nobody wants to touch.
Yes, I found where that is coming from.
TypeScript
React JS
jQuery
React Native
HTML
PHP
SASS
Dev
#011
Livia
Builds front-end pieces with focus, patience, and just enough JavaScript bravery to keep the interface moving.
I make JavaScript behave. Most days.
React.js
JavaScript
Dev
#012
Rebeca
Makes the front end feel organized, usable, and less like a group project between browsers, breakpoints, and JavaScript.
If the layout breaks, I probably already know why.
React.js
Front-End Development
Next.js
JavaScript
UI/UX
#013
Nemanja
This title gets less accurate every week. At this pace, it is only a matter of time before it officially becomes Vibe Coder.
Design system first. Vibes second.
UI/UX
Design systems
Vibe coding
Growth
#014
Samanta
Officially Marketing, unofficially UI research, WordPress detective work, and data entry across 47 mysterious domains. Somehow still expected to "just post something" at the end.
Which domain is this one again?
Marketing
Research
WordPress
Founder note
// from the founder
We strive to take on difficult and challenging projects while provide strong technical solutions. Working with WordPress and mobile applications has been thrilling and the future continues to be bright for these technologies. WordPress in particular is an extremely powerful and flexible platform that is ever improving and extremely customizable. We look forward to taking on any challenge you have for us…
Jeff Schreibman
Founder, RTW - 2012
Built for
Systems that last
Work includes
CMS / apps / dashboards
Useful when
The work gets messy
Default mode
Plan / build / support
// Ready when you are
Bring us the technical mess. We’ll shape it into scope.
A fragile site, a manual workflow, a dashboard nobody trusts, an AI idea without guardrails, or a support gap nobody owns. We help turn that kind of mess into scope.
