Current Loading

Sorry, no fun pictures of outings to post…  tho the waves have picked up here in Santa Cruz.

Contract work picked up a bit too.  In the immediate we are pretty committed…  but always on the lookout for FTE and LabVIEW work.

  • 10hrs/week – OEM Automotive in Fremont (Startup)
  • 10hrs/week – R&D / Sevcon support in La Selva Beach (Startup)
  • 1-10hrs/week – Robotics in Palo Alto (Startup)
  • 5hrs/week – LabVIEW  (YEA!!!!!)

Our stated intent is still to move toward FTE work (in any field) or LabVIEW work (of any kind be that FTE, Retainer, Contract, Consult, or in Education).


-the management

To the prospective Full Time Employer

I am currently seeking full time employment, in the following order of preference:

  • Test Engineering in a position that is heavy in LabView.
    • R&D, Lab Support/Management/Tooling, Qualification, Production testing, component -> PCB -> System level.  If it involves solving problems with LabView I am in.
  • Full Stack Battery Management Systems Engineering
    • Architecting, down selection, component spec’ing, circuit design, PCB layout, proof of concept and first runs, production intent hardware, full production, legacy support, retrofit, and reverse engineering.
  • Systems Engineering in the Electric Vehicle market or DC of any kind
    • Battery powered systems low power to high power.

Schindler Engineering   is not currently    committed to any long term efforts which can not be tied up inside of a week.  We have a few short term deliverables which are at 90% and we are hesitant to make further comittments before investigating opportunities to work under the umbrella of a larger company.

“We” (Schindler Engineering) are currently only responsible to myself and our Accountant.  Our accountant has opportunities for FTE work and our contracting associates are all pretty well placed in paying work off site.


Rational for seeking Full Time Work:

Contracting and Consulting affords us a lot of flexibility…  but it comes with a very large overhead, inconsistent finances, and most importantly a risk level which is above what we can currently tolerate.  We have financial obligations and stability needs which are incompatible with the ups and downs of Startup Life.

I am in a position to commit to FTE work for a length of time up to 10 years and I would prefer to target positions which will last no less than 2 years.  Of course life happens…  but we always aim at what we want to hit.

I can work On Site anywhere in the Bay Area 40hrs a week with On-Call from Santa Cruz County (40 minute response time other than rush hour).

I am flexible around compensation depending on requirements.  If I need to be on site, on a fixed schedule, on hard deadlines, doing tough work, managing risk, <[in the critical path…]> then I need to earn market rates.  If on the other hand…  there is flexibility for me to work an alternative schedule, work from home part time, to work outside of the critical path, to do work which involves low stress/low risk…  we can afford to work a bit under market.  The key factor in salary requirements is how tied into the schedule I am and how much flexibility there is for my family needs.

At this point in my career I should be transitioning into management… (which is as critical path as it gets…) but I still really enjoy engineering work (which often can involve parallel path activities…) so I will entertain any opportunity for the right company.

You will start to see a transition in the Schindler Engineering blog to focus more on LabView, Test Engineering, BMS architecting, and other activities which develop quickly (meaning I need to stay up to date on the latest to be relevant).

Feel Free to check in on some highlights of my experience at LinkedIn:

Being that I have over 15 years post bachelor experience…  there is far more unlisted than listed at this point.

thanks,   -Patrick

Kayak Power….  V2 in the water

Last night (after sunset) we were able to breach the harbor mouth under new power.

In the pics you can see the vintage Minn Kota that powered V1.  Tiny motor, tiny prop.  Next to that is a big upgrade courteously of a Masterguide bow mount.

(note:  I apologize for the pictures.  My Nexus 5X is finally giving up the ghost after a very hard life.  It was an excellent phone.)

Both of those motors are 12V rated…  but obviously the one on the right is capable of putting on a better performance.

We picked up a bow mount Masterguide (remote control steering and all) for $26 at the Fleamarket.  It had a bad steering gear box and trouble with the PCB board.

No problem…  all we wanted was the lower unit.  We disassembled it, along with the vintage Minn Kota, and put something new together.  The Minn Kota donated only the mounting hardware.  Control is handled by a 300A AXE controller.

This is a progress pic (of course that stuff needs to be ocean resistant…) but in it you can see the basic layout:

Battery:  6S 6P 35C Hobby King packs.  This works out to 22.2V @ 18Ah so capable of 20KW burst and almost 1kA.

Controller:  AXE 300A controller capable of 16V to 60V…  so Ebike battery compatible.

Throttle:  Zero pulldown 5K Magura.  Note that you need to configure this to run 5K to 0K (to avoid WOT on a disconnected throttle) and be sure to enable the interlock on startup (wont run until it sees 0% on the throttle).  Take your time with the Magura and make sure you get a clean 5Kohms to 0ohms…  they can be calibrated and many people change the output range to match a standard 1.2V to 4.2V hall throttle.

Wiring:  Coming out of the lower unit were 4 wires…  the heavy RED and BLACK are direct motor connections.  The Green and Blue can be ignored as they go to a mosfet pack that we wont be using.  (The AXE controller handles all our PWM needs)

We connectorized everything up with Anderson PP45’s in parallel (2P can handle 100A continuous into 10AWG) and SB120’s…  which are rated for 240A @ 600V.  Balance taps are paralleled at the cell level using MethTek parallel boards.  Currently there is no BMS in the system, we are working on that.

As a rule of thumb…  doubling voltage quadruples power.  In this case we doubled voltage and sized up the prop considerably…  leading to a huge performance increase.  The speed and acceleration is night and day.  We will grab some GoPro video some time this week.

V3 will be a Gen 4 Sevcon along with a 75-7…  but that adds all sorts of complexity that we are not in a position to tackle yet.  Prop angle, waterproofing, steering….


Sevcon Gen 4 Support

We are to the point where we can offer professional Sevcon Gen 4 support.

We have invested over a year into the minutia of this.  I dont want to make it sound complicated (because we can simplify it for you) but working with Sevcon hardware really does require professional support unless you are in a position to tool up, learn the tools, and invest the time.

We have an OEM relationship with Sevcon.

We have up to date licensed copies of DVT.

We can load DLD files.

We can read, modify, and write DCF files.

We can help you to transition your existing system from a Size 4 controller over to a Size 6 controller (for significant performance gains).

We can support you with Sin/Cos encoders, UVW encoders, wiring and pin mapping, basic tuning, and some Dyno tuning where appropriate.

We have a line of custom harnesses built to or above OEM Automotive spec that (in combination with a DCF tuned to your hardware set) can make for a turn-key setup.

We can support any existing Zero Motorcycles gear as well as any equipment purchased from  We are working on supporting other existing motors like those found at Joby, Jozztek, and others.

We would like to support Boating applications, Kart applications, custom Motorcycle and Enclosed medium weight EV applications.  We are even starting to support some E-Flight applications (tho those require a higher level or rigor to assure air safety).

Currently we are working under the umbrella of an OEM as we develop a new Power Systems branch.  Until that venture is funded this is somewhat grass roots.

Hourly consultation is available – either over the phone or email.  Email is suggested as it tends to be more productive.  If you can clearly state what you have, where you are at, and where you want to go…  we can make suggestions as to other OEM’s and niche shops we work with.

We can suggest parts for safety and reliability (like throttles with interlocks) and inform you as to what you will need if you want to support yourself… or we can steer you toward one of our turn-key options

The key tools are:

  • Recent version of DVT
  • Proper galvanically isolated CAN programming device (IXXAT or Clone)
  • Professional 2 step crimpers and pins for Sevcon 35pin connector
  • Appropriate hall sensor and means to calibrate to motor
  • Harnessing and matching DCF

If you are looking for a turn-key solution…  or just looking for some help mastering what you already have, we are available.

At the moment we are working on a custom version of the ClearView iterface that will alleviate the need for DVT and an IXXAT such that customers can collect data and make minor changes without having to loop us in.

Feel free to reach out to us in the Contacts section.

All due respect to those who came before us like Ryan Biffard of Zero Motorcycles, the team at Thunderstruck-EV for their work supporting Sevcon, Steve at Jozztek in the UK for his EV expertise, and all the others who helped get us to where we are at.

Respect also to the companies where I have worked that first introduced me to Sevcon gear in their products – namely Zero Motorcycles and Electric Movement.



Schindler Engineering Adventure 002

This adventure has been all about BOATING!

Since we moved closer to the sea (we are a block from the harbor small-craft launch now…) interests have shifted to powered water craft.  Where we are ultimately headed is a Zero Motorcycles 75-7 driven by a Sevcon Gen 4 in size 6…  but before we jump into that we had to freshen up on some basics.

Here is a pic of the Size 6 Sevcon with a custom harness that we spec’ed and built from scratch over at Calfee Design

Of course that all gets split-sleeve for abrasion and overall aesthetic but you get the idea.

The motor will look a little something like this:

That is an up-cycled Zero motor that has been carbon wrapped on a lathe and drilled for ventilation.  That particular motor has an interesting future …  ours will be a bit different.



The Transom is the mounting point on your boat for the motor.  In this case…  a small electric outboard you will recognize as a “Trolling Motor”.  These motors can be quite over-volt friendly…

You will notice that is a REALLY ROUGHED OUT example.  We built this from no plans in 45 minutes using nothing but some cabinet wood we found in the garage, an angle grinder (no saw!), and a drill.

The assembly mates to the plastic Kayak via blind rubber nuts…  you basically over drill, insert, and expand.  They work quite well and do not damage the kayak in the process.

In the spirit of ROUGHING OUT A PROOF OF CONCEPT we picked that Trolling motor up for free in Laselva, nabbed the battery out of my car, and headed for the harbor for a test run.


Testing, testing, testing…  I cant say it enough!

At Schindler Engineering – before we dive head first into an expensive venture we spend AT LEAST 20% or 30% of our time bounding the problem.  We start simple and cheap…  with a test that will help us understand what sort of hurtles we will see as we start to scale.

If the 2 person Kayak is hard to handle on 30lbs of thrust…  it will be unmanageable with 300lbs.  🙂   Seems obvious, but you would be surprised at how often we have seen a system getting finishing touches that fundamentally just will not function well.

So with the boat in the water and a better understanding of how it will load down under the weight, how the steering will feel, whether it will need stabilization…  we decided further testing was in order.

Off to Washington…  our official test site for all things ridiculous.

Here is a shot of our test fleet:

The Trusty Aluminum cruiser, the not so trusty foam floater, and the ultralight inflatable.

For the record…  the foam bit of business up there was built by Mathew R. back around 2013.  We were on holiday and I challenged him to make a seaworthy vessel in less than 15 minutes.  That’s what he came up with… quite clever…  and so as soon as he announced completion I tied a rope to it, asked him to board, and took off across the canal!  Lol…  We motored until the battery died and then I rowed him back in.  Confirmed…  his vessel was indeed seaworthy.


Weight and draft is everything…  followed closely by steering and the ability to stay afloat.  This fine vehicle can be hand carried with ease but is hell to steer.  Right off it is clear that we will need a boat which is not flat bottom if we are going to harness the Zero Power Train…

It needs to be light…  it needs to hydroplane to some degree…  it needs to turn on a dime WITHOUT FLIPPING.  (Reference future photo which is not yet taken of the 5 gallon jugs on a boom we will soon add to the test Kayak)

So…  all of these rigs have been slow so far

(Unlike this snail we found at low tide which when fully extended was the size of a cantelope)

But….  just like a goat in a diaper with a cast on its leg at a laundromat…

Good things start small, Fast things start slow, and boats with enough power never sink!

Until next time…  on Adventure


Learn to use Python in a day…

Admittedly I am late to the game with Python.  That said, I have trained and qualified myself in the understanding and use of it.

(NOTE:  I watch these videos at 2X speed…  you may want to start at 1.5X if you are not completely comfortable with programming paradigms)

I started by following this 17 video sequence to understand the new syntax and rules.  Its all basic…  but if you are coming from a different language it can be very confusing at first.  I suggest taking the time to step through the basic videos…  not because you don’t know how to set up an if/else structure…  but simply to get comfortable with the style of Python.

Having a lot of experience using languages that are tightly type cast, agnostic to spacing, and deterministic…  my first response to Python was “Trouble – ACK!”

Type casting was traditionally very important for ensuring compiled results came out as expected…  older compilers would let get into trouble in any number of ways.  Compilers these days are orders of magnitude better…  so…  the harsh rules of the past are no longer relevant.

I accept this as a superior tool for quick collaborative development.

Many good changes to legacy methods have been developed and refined (even though a few stinkers snuck through…  like the confusing for new folks += ) and I have decided that I like the language and want to work with it.

Now…  for some more advanced use cases.


Python… how to decompile it

So you want to see the goodies inside of a PYO or PYC compiled Python file (PY) ???  

If so…  you may.  Its byte code (and not true compiled code…) so it is trivial to decompile into something readable that will get you the information you need or want.

Disclaimer:   Too the nOoB

Now I have been doing this since we were writing code in Assembly…  HEX, Assembly, C, C++, Java…  all languages are essentially the same.  I am old and crusty so I get to do things like this ethically.  We learned in the late 90’s by passing arguments back and forth across the stack between ASM and Turbo C (which we installed with floppy disks…).  The forum named “Stack Overflow”…  well…  I am one of those old guys who had to actually count the bytes in the stack and insert carefully.  I know all about overflowing stacks and writing random information to places it should not be.


1 – Install both Python 2 and Python 3

You will need both to be compliant with legacy and current designs.


2 – Install an IDE of your choice.



3 – Set your PATH variable so that you can execute a command prompt from any window:

RHC start menu, Control panel.  Search “path” and select “edit system environment variables”.  Create a new variable PATH and aim it at your python install.  Separate by semi colon.  Use this tutorial:

Now you are all set…
To run Python from any folder…  click FILE and select CMD.  You will have avoided typing in a long path and much time has been saved.

To run python just type it.

To run a specific version type

py -2

py -3

To run 2 or 3 respectively.


4 – Now…  none of that was required…  but I wanted you to install python so…  now you have.  😉


Meat and potatoes:

I tried 2 of the command line tools.  They were obnoxious…  but there is a GUI that rides on top of them and handles the details for you (if you are a python nOoB like me).

The tool to use is this one:   Easy Python Decompiler

Test Results:

For Python 2 it works.

For Python 3 it APPEARS to crash…  BUT ACTUALLY WORKS…  its simple point and click…  then the file you want magically appears in the source folder.


There you go.  Dont get in trouble and only call the cops if you have to…  Authority figures should be reserved for emergency situations.  Anything else…  I am sure we can handle.


Understanding Test and Measurement

There is a lot of confusion around Test and Measurement…  especially where Qualification and Manufacturing Pedigree is concerned.  I will break it down here into 3 categories and explain why R&D testing is cheap and why costs go up when you step into production.


R&D, Qualification, and Production Testing


R&D Testing:

There are few controls around this sort of test equipment and cheap hobby tools usually do just fine.  A $200 all-in-one USB based device that offers Analog Input, Digital I/O, timers, and maybe some Analog Output can provide all the stimulus and data collection you need to ring out bugs and make good progress toward a proof of concept.

Generally speaking these tools are not calibrated, they are not modular or expandable (for re-use on the line), they are not rugged or reliable, they depend on a PC being connected, they are not capable of holding Precision (hardware timing), they are limited in sampling rate, and generally speaking they are not reliable or fit for making statements about Precision and Accuracy.

Hobby grade tools are more than sufficient for R&D work…  because the risks involved are relatively low and any engineering facility will have some quality lab equipment (possibly shared) to validate test results.  A good Meter (Fluke) and a high speed scope (ideally isolated) are the real tools of the trade…  but they are expensive and often shared…  so folks set up with USB boxes at their desk.  The Take Home Concept is that the cost of mistakes starts going up by Orders of Magnitude as you come out of R&D and into Production… 


Qualification Testing:

When we talk about Qualification Testing…  we are talking about stepping out of R&D.  We are talking about freezing a design and developing metrics to make statements about Accuracy and Precision such that we can confidently state that if we make 1,000 of these…  we wont end up doing rework operations multiplied by 1,000.

A qualification tester should be Calibrated or of a known quality standard.  It should be reconfigurable…  as its life cycle is usually short.  It should be hardware timed (precise).  It should be high resolution (accurate) and isolated….  such that it is capable of picking up low level noise and does not appreciably affect the circuit under test.

A Qualification tester is the tool used to develop confidence in a design before committing to volume production.  Generally it is best if a third party develops a Qual tester so as to uncover blind spots that may be intentionally or unintentionally missed by the R&D Engineer.  More specifically…  a Qualification tester is built strictly to a set of requirements.  Think of Requirements as a series of transfer functions.  A black box with input, behavior, and output…  such that a series of behaviors and functions can be listed and tested.  Requirements are negotiated and can be lax or rigorous.

There are infinite ways to define requirements…  and infinitely more ways to test to those requirements…  but the job of a Qual tester is to state unequivocally that a set of production intent hardware meet or exceed the stated requirements (yes…  I understand that is a bit circular).  I can go on ad nauseum but I will spare you.

Qualification is where R&D lets go of a design…  where any problems which were previously masked are uncovered…  and where we build absolute confidence in our readiness for Production.



Production Testing:

Sometimes folks mix Qualification into Production Testing…  but really…  a Production tester should be the simplest, cheapest, way to display a RED LIGHT or a GREEN LIGHT such that a part can move on to next assembly or be sent back for rework.

Production testers look for things that change…  like impurities in conformal coatings which develop as leakage currents.  Parts which come in out of spec due to counterfeit production or poor storage.  PCB’s which have missing, extra, or inconsistent electrical connections.  A thousand solder points. …  Its the job of the Production Department to drive costs down as far as possible…  and if production is doing their job…  at some point unacceptable quality will be reached.  Its the production tester that sets the boundaries for this exercise.

Yield …  there is no such thing as 100% on an efficient production line.  Some number of widgets will always go back for rework.  Its the job of the production tester to provide a “troubleshooting guide” to speed up this process.  At a minimum a production tester should be able to indicate the test or tests which failed.  The rework tech, with time, can interpret these results, identify problems in process, and make corrections to improve yield while keeping costs down.

UI (User Interface or User Experience) is very important in a production tester.  It has to be absolutely dummy proof.  It has to be BOMB PROOF…  such that a guy can be picked up at a temp agency, put to work, and no impact on quality can be measured.  There must be no correlation between the test operator and the final product.

A production tester must scale well.  If production is to improve it either must run faster (in relation to the rest of the processes such that it is not a big impact on the critical path) or it must be able to be cheaply and quickly duplicated.

Again I could go on ad nauseum.



Every engineer who is successful already has their preferred set of R&D tools.  Usually this is something they became familiar with in school, at home, or at a previous job.  The tools work and everything is great.

Where things get hairy and confusing is when its time to Qualify a design and move into Production.  This is the point where most costly mistakes are made.

R&D/Proof of Concept, Functional Prototype/Production Intent Hardware, Short Run Production/Full Production

The cost of mistakes goes up by an order of magnitude as we break out of R&D.  A $10 mistake becomes a $100 mistake…  then the same sort of mistake becomes a $1000 mistake…  MULTIPLIED BY UNITS IN PRODUCTION!

I cant stress this enough… and every business minded lean-machine out there thinks they can jump the gap and hover directly from R&D into successful Production.  I am not a “hater” – its possible – but it is also highly likely that any attempt to avoid due diligence will just result in the money being spent anyway…  then spent again.  Infinite examples available…


OK – So what do I buy to make this magic happen and how much does it cost?

Anyhow – my point was originally to introduce you to some of the hardware tools that I use.  Lets skip R&D tools…  since that is really a personal preference…  and review proper tooling for Quality.

This breaks down into two major categories:  Big Budget and Small Budget

Big Budget is a laboratory setting where progress is measured in years and quality is non-negotiable.  Small budget is probably where you are…  where you just need to get something going for as little investment as possible.

Big Budget looks like NI PXI… and $50k is the sort of spend you are looking at.

Small Budget looks like NI cRio…  and $5k is actually a reasonable spend for a system (if you buy used and are thrifty)

Before I call out hardware…  lets take a moment to clarify an assumption.

<It is my belief that a system should be configured as follows:  Windows UI linked to a Real Time or FPGA control loop. 
User Interface:  This can run on a standard windows box and generally everything is fine.  This part of the system really does no work other than taking commands and displaying results.  This machine can be local or remote….  headless and integrated or user facing.  This machine protects the Real Time hardware from non-deterministic behavior.  Its a buffer…  and an interface.

Test Hardware:  This part of the system MUST be deterministic to be reliable.  At the slow end…  maybe a 1ms RTOS (Real Time Operating System) control loop.  At the fast end…  maybe a 1uS FPGA control loop.  This means that all outputs and all inputs are guaranteed to be precise and perfectly repeatable over time.  It means that sufficient buffering is in place and that even if there is some sort of lag or delay in the UI…  that the actual UUT (Unit Under Test) is under tight control and results can be compared apples to apples over hundreds or thousands of cycles.

So tying back in…  PXI is a high end chassis that allows this sort of thing.  cRio is a smaller/cheaper/more rugged version of this – and that is what we will focus on for the final chapter of this nerd-rant.



Without turning this into some sort of National Instruments commercial…  It can be described as a back-plane or chassis with a built in controller.  There are 4 or 8 slots where cards can be plugged in (AI, AO, DI, DO, II, you name it…  these are measurement heads…  with 1-32 ports….)  and the chassis is expandable as needed to host more than 8 cards.

At the head of the chassis is either an embedded FPGA, an RTOS controller, or both.  This is the key to success…  as the system can run headless with no external connection to a PC or network – therefor little to no chance of latency related issues…  which are the sort of bugs that pop up after hours, days, months, or years to bite you in the ass.

The RTOS or FPGA system is programmed with a behavior loop.  Said loop runs hell or high water.  The system can take ques and commands…  and can provide buffered data.

  • A chassis is purchased ($500)
  • Appropriate cards are purchased ($50 – $500 each)
  • A windows box or laptop is purchased ($400)
  • Licenses to run the UI, RTOS, and FPGA are obtained (Negotiable – $2k to $5k…  but that is something that I buy and use over and over for different jobs.)

Buying these things new is a killer…  but …  the used market is looking GREAT.  Here are some examples from Ebay.

(Best value is in buying 2 or 3 package deals then breaking the systems up as needed)

cRio Chassis with a Real Time controller and 7 I/O cards –   $2,100.00 USD

8 slots and a controller  –  $500.00 USD

8 slots and a controller – $600.00 USD

Controller – $100 USD

32 Channel, +/-10V, 16bit, 250kS/s Analog Input   – $230.00 USD

RTOS, FPGA, 8 slots – $450.00 USD

So…  the Angel Investor hurtle to launch this sort of activity is about $10k….. $5k to get into the hardware and $5k to get a maxed out license.  A license works forever but can be upgraded as new features are released.  Legacy hardware is supported on the timetable of decades.

The cost of initial setup and support on a system like this is reverse expo.  Once a system is in place a Junior Engineer with minimal oversight should be able to expand, duplicate, or otherwise modify at a burn of about $50/hr.  Initial setup one time burns at $100/hr.  There are A LOT of experts out there who can pick up on a system and modify it in short order…  that’s why NI is so popular…  because it is *VERY EASY TO FOLLOW IN THE FOOTSTEPS* of the previous engineer.

Until next time…  Eat your broccoli and brush your teeth.  I am off to get paid to test stuff.

-Patrick Schindler

Transparency in Rates

We don’t like surprises…  and neither do you.

This is the focus… everything else is a distraction

(Those fingernail biting 12 hour days around an Engineering Release where everything that can go wrong finally does and everything that worked consistently suddenly does not…  that’s where real engineers shine)


There are enough surprises along the road from R&D to Production to keep us all thrilled.  We don’t need any surprises around budget.  Understanding burn rate is the easy part.  Understanding and projecting the undefined around engineering is the hard part…  and should be the focus of engineers.



We have collected rates for our partners and we can help with pass-thru billing on 1099 work.  We can handle all the accounting, invoicing, purchasing reimbursements, hours tracking, and serve as a single POC for Scheduling.

We have negotiated with and have a few more Trusted Associates to post…  but…  those are non-billable hours for us (updating the website…  what a pain… ) and we get to it as we have time.

Here are my rates (Patrick Schindler)

$***/hr for turn-key service.  Consider this a shop rate or “hit the ground running” rate for walking into any developing situation or launching a startup company.  You would not believe what I have dealt with and what I have seen.

$***/hr for engineering inside of a pre-existing complex.  This is the rate I charge to operate inside of your well tuned machine where I don’t have to recruit, hire, fire, or make decisions for you.  You are in charge, my part is clear, and I don’t lose sleep at night.

$**/hr is my joint-venture rate.   This is a rock-bottom “friend price” or “venture price” for working with growing companies THAT MAY PAY OUT BIG IN THE FUTURE… and that we have an ongoing history or trust relationship with.  Companies that we either helped launch, helped to launch us, or otherwise register as awesome and an honor to work with…  but who are struggling or otherwise not in a position to pay appropriate rates.


The truth is that most of the time we are called in once things are already behind schedule, in trouble, or otherwise requiring immediate response.  I would love to say that folks bring us in early and things run smooth…  but it just is not always that way in the LEAN startup environment.

I have worked in the most adverse and upside down environments you can possibly imagine.  From sitting on buckets in a cold garage (many of them…)  to having my own lab behind layers of security at a National Laboratory.

What I can promise you is clear communications and no bullshit.  If you seek bullshit I charge double (or even triple) for that service… where I am reluctantly experienced due to my time in the field.